The FreeEOS project has a number of users that use a variety of different
lapack-related libraries which are named in a variety of ways. Because the
FindBLAS.cmake and FindLAPACK.cmake modules provided by Jan Woetzel at
http://www.mip.informatik.uni-kiel.de/~jw/cmake/CMakeModules/ do not deal
with
Bill Hoffman wrote:
Basically, there are two types of generators, single build type per
build tree, and multi- build type per tree. The variables that are
useful for that are here:
CMAKE_BUILD_TYPE is used by makefile generators or any future
generator that supports one build type per buil
Sam Miller wrote:
I am trying to convert an hand-rolled Makefile build system into CMake.
The project itself is a subset of a larger project, which uses a
Make.rules file for various cross compilation rules and install
directories. Is there any way to include this Make.rules file into the
Makefi
David Cole wrote:
Put the -D args *before* the -P -- it'll work like you expect then...
I've added content bug #4372 on this issue. The order dependency should
be documented.
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http:
Indeed, the first GUID in the project definition line indicates the
project type (C++, C#, Visual Basic...). The
INCLUDE_EXTERNAL_MSPROJECT command needs to change the GUID based on
the project type.
Thanks for pointing this out.. ;) I just added some C# projects to our
solution, quite handy.
He
I'm having trouble using CMake in a project with mixed Fortran and C code
and I'm hoping someone here can help. I am using Visual Studio 2005 and
Intel Visual Fortran 9.1. Sorry for the length of this post.
1) The test for the Fortran compiler is failing indicating a broken compiler.
It br
Put the -D args *before* the -P -- it'll work like you expect then...
:-)
David
On 1/25/07, Abe Stephens <[EMAIL PROTECTED]> wrote:
Is there a way to pass command line arguments into variables when using
"cmake -P"?
I tried "cmake -P foo.cmake -D var=value" but that didn't work. I could
do it
Is there a way to pass command line arguments into variables when using
"cmake -P"?
I tried "cmake -P foo.cmake -D var=value" but that didn't work. I could
do it using configure file, but that seems overly complicated.
Thanks-
Abe
___
CMake mailing
Hi,
I use a custom preprocessor to compile some of my files. For that to
work I create custom commands, so that for each c file, a gen.c file
is produced. Only the generated files are compiled. There's a
dependency between the gen.c and the c file, so that when the c file
changes the gen.c file i
I am trying to convert an hand-rolled Makefile build system into CMake.
The project itself is a subset of a larger project, which uses a
Make.rules file for various cross compilation rules and install
directories. Is there any way to include this Make.rules file into the
Makefile generated by CMak
Brandon J. Van Every wrote:
In our PCRE library, pcre_ucp_findchar.c has
#include "ucp_findchar.c"
Will CMake automagically detect this dependency? I think it would be
incorrect to list ucp_findchar.c as a source file, as we don't want an
object file to result. I suppose I'll do ADD_DEPENDE
Brandon J. Van Every wrote:
Eric Noulard wrote:
Is there a way to build both shared AND static
in a single build
Yes. However, you'll probably need to compile them in separate
directories to prevent collisions between object files. The Chicken
CMake build http://www.call-with-current-con
Brandon J. Van Every wrote:
I added the following notation to the Useful Variables page of the wiki:
http://www.cmake.org/Wiki/CMake_Useful_Variables#Compilers_and_Tools
"Note that CMAKE_BUILD_TYPE is not initialized with a readable value
at configuration time. This is because the user is free
I added the following notation to the Useful Variables page of the wiki:
http://www.cmake.org/Wiki/CMake_Useful_Variables#Compilers_and_Tools
"Note that CMAKE_BUILD_TYPE is not initialized with a readable value at
configuration time. This is because the user is free to select a build
type at bu
Eric Noulard wrote:
> 2007/1/25, Andreas Schneider <[EMAIL PROTECTED]>:
>> Eric Noulard wrote:
>> > Is there a way to build both shared AND static
>>
>> Hi Eric,
>>
>> yes there is. From the cmake documentation:
>>
>> SET_TARGET_PROPERTIES
>>
>> When a library is built CMake by default generates co
Eric Noulard wrote:
Is there a way to build both shared AND static
in a single build
Yes. However, you'll probably need to compile them in separate
directories to prevent collisions between object files. The Chicken
CMake build http://www.call-with-current-continuation.org/index.html has
In our PCRE library, pcre_ucp_findchar.c has
#include "ucp_findchar.c"
Will CMake automagically detect this dependency? I think it would be
incorrect to list ucp_findchar.c as a source file, as we don't want an
object file to result. I suppose I'll do ADD_DEPENDENCIES if they're no
automagi
2007/1/25, Andreas Schneider <[EMAIL PROTECTED]>:
Eric Noulard wrote:
> Is there a way to build both shared AND static
Hi Eric,
yes there is. From the cmake documentation:
SET_TARGET_PROPERTIES
When a library is built CMake by default generates code to
remove any exist
Bill Hoffman wrote:
Brandon J. Van Every wrote:
Bill Hoffman wrote:
You can not use FIND_* stuff because the files will not be there.
There is a risk that cmake could change where the .o files are put.
To mitigate that risk, I would recommend setting up everything with
variables. You a
Quoting Alexander Neundorf <[EMAIL PROTECTED]>:
Von: Peter Soetens <[EMAIL PROTECTED]>
Hi,
I'm having this situation: a source file property is set in a subdir
(GENERATED true), but when the source file property is read again in the
root directory, it is no longer present on that file. Is th
Hi, all.
I try use last CMake 2.4.6
It fails generate MSYS Makefiles. At the same time version 2.4.3 has NO
such problem.
I have all last updates for MSYS and for MinGW.
System is Windows XP SP2
Hear is cmake log:
cmake -G "MSYS Makefiles" ..
-- Check for working C compiler:
Von: Peter Soetens <[EMAIL PROTECTED]>
> Hi,
>
> I'm having this situation: a source file property is set in a subdir
> (GENERATED true), but when the source file property is read again in the
> root directory, it is no longer present on that file. Is this intentional
> behaviour ?
>
> It's n
Hi,
I'm having this situation: a source file property is set in a subdir
(GENERATED true), but when the source file property is read again in the
root directory, it is no longer present on that file. Is this intentional
behaviour ?
It's not documented that the property on files scope is 'local'
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
Hi,
I would like to obtain library name through:
GET_TARGET_PROPERTY(library_name MyLibraryProject ${CMAKE_
BUILD_TYPE}_LOCATION)
This works on Linux. However, ${CMAKE_ BUILD_TYPE} doesn't get set in
MSVC.
How can I
Brandon J. Van Every wrote:
Bill Hoffman wrote:
You can not use FIND_* stuff because the files will not be there.
There is a risk that cmake could change where the .o files are put.
To mitigate that risk, I would recommend setting up everything with
variables. You already have these
${
Is there a way to build both shared AND static
in a single build or should I run 2 builds
one with
BUILD_SHARED_LIBS ON
and another one with
BUILD_SHARED_LIBS OFF
I would something like:
BUILD_SHARED_LIBS BOTH :))
Using this scheme we can deliver both static and shared libs
to our users.
--
Er
Hi David,
thanks for reply, even it's 2 months later it was still helpful for me. I've
followed your steps and it works for me! Unfortunately I cannot reproduce
what I have done wrong 2 months ago, but I guess the main difference to your
approach is that I have tried to use my own NSIS.template.in
27 matches
Mail list logo
