err, actually this doesn't seem to work either. CMake doesn't seem to honor
the LINK_FLAGS property when linking a statis library.
Bryan
[EMAIL PROTECTED] wrote:
> I think this will work for what a need to do now, but it seems to be awful
> lot of work for something that should be pretty
I think this will work for what a need to do now, but it seems to be awful lot
of work for something that should be pretty straight forward to do. Would it
be worthwhile to rethink how CMake links static libraries under windows?
Bryan Walsh
Ben Ratzlaff <[EMAIL PROTECTED]> wrote:
> Here
Part of my objection is that I want to limit how many in which libraries I have
to distribute.
My project looks some thing like this:
main_src/
main_exe (depends on main_shared_library)
main_shared_library (depends on my_static_library_facade)
my_static_library_facade
Hi All,
I have a static library that I'm trying to compile and link under windows. It
depends on other static libraries. It appears that the default behavior of
cmake is to defer the linking of the dependencies until they are needed by a
dll or executable. There is no way under cmake that I
Is there any way to set windows registry keys with cpack. For example I would
like to associate a file extension with my application.
On the wiki I see there is a CPACK_PACKAGE_INSTALL_REGISTRY_KEY variable, but
if I understand it right, it just sets where keys internal to cpack will get
set u
I could do that but I do not think I should have to. That would require me to
restructure a fair amount of the project.
Everything I need is already built by cmake as is it is just a linking problem
that appears on windows only.
Thanks,
Bryan
Filipe Sousa <[EMAIL PROTECTED]> wrote:
> [
Hi All,
I have a project in which I build a main application and several plugins
(modules). My main cmake file look something like this:
ADD_SUBDIRECTORY(MainApp)
ADD_SUBDIRECTORY(plugins/Plugin1)
ADD_SUBDIRECTORY(plugins/Plugin2)
...
Plugin1 cmakes file looks like this:
PROJECT(Plugin1)
INCLU
Hi,
I'm trying to construct a list of external libraries. This list needs to
include the full path and name of each library. This list is to be used with
the INSTALL(FILE) command. I'm trying to use FIND_LIBRARY inside a FOREACH
loop command to accomplish this. For example:
SET (LIBS ${OSG
"William A. Hoffman" <[EMAIL PROTECTED]> wrote:
> OK, I am going to revert my changes. It causes the lex to go
> into an infinite loop and I don't have time to track it down now.
>
> -Bill
>
Were you having problems with a fixed or free formatted file? Is it something
you can send to
"William A. Hoffman" <[EMAIL PROTECTED]> wrote:
>
> Will the change I just checked into CVS work for you?
>
> -Bill
>
Yeah, sorry I wrote my email before seeing that you had committed a change.
Bryan
___
CMake mailing list
CMake@cmake.org
h
Brad King <[EMAIL PROTECTED]> wrote:
>
> FYI, there is a bug report for this problem:
>
> http://www.cmake.org/Bug/bug.php?op=show&bugid=3109
>
> I briefly looked at fixing it but got stuck on the free-format versus
> fixed-format parsing. Unfortunately I have no time for this bug now.
>
Something like this could be done in cmDependsFortranLexer.in.l
...
%option reentrant
%option noyywrap
%pointer
%s free_fmt fixed_fmt
%x str_sq str_dq
%%
%{
bool fixed = cmDependsFortranParser_isFixedFormat(yyextra);
if (fixed)
BEGIN(fixed_fmt);
%}
\" {
cmDep
Hi Alan,
My knowledgebase of fortran lies with fixed format f77 fortran, so your right
the solution below only works for fixed format Fortran. There is currently
nothing in the .l file to set the state, so the line:
^[cC*dD].*\n { return EOSTMT; }
never gets triggered. Having only worked
Thanks Karl, that got me looking in the right direction:
Changing the line
^[cC*dD].*\n { return EOSTMT; }
to:
^[cC*dD].*\n { return EOSTMT; }
in cmDependsFortranLexer.in.y fixes the problem. This forces the parser to
ignore comment lines.
I also discovered that include paths are not search
Thanks Bill that worked great! I was missing the step about deleting the cache
file.
The next problem that I ran into was various mod.proxy dependency issues. I
saw an earlier thread on this but no solution was reached. I ended up
commenting out the module dependency code under cmDependsFort
Hi,
I'm trying to get a mixed C++ and fortran project up and going using the Intel
Fortran compiler.
I have a CMakeLists.txt file that looks something like this:
SET (TARGET ProjectName)
PROJECT(${TARGET} CXX Fortran)
SET (SRCS
.
.
.
)
ADD_LIBRARY(${TARGET} SHARED ${SRCS})
SET_TARGET
16 matches
Mail list logo
