, Jonnalagadda (IE10) wrote:
...
Does this work with all types of modules? I mean for those modules
that
are automatically included like find packages, compiler settings,
platform settings etc?
Can you please explain a bit more in detail what you mean ?
Some files will be taken from ${CMAKE_ROOT
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Neundorf
Sent: Tuesday, May 22, 2007 7:35 PM
To: cmake@cmake.org
Subject: Re: [CMake] [Dev] CMake 2.5-20070519 and tool chain support
So to make it short I suggest to set CMAKE_SYSTEM_NAME
, Jonnalagadda (IE10) wrote:
...
It would make it very easy for one to distribute the project with
the
respective cmake support files when cmake officially does not
support
the configuration. Or if the for some reason one wants to override
the
default configuration.
This should also be possible
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Trevor Kellaway
Sent: Thursday, May 10, 2007 4:33 AM
To: cmake@cmake.org
Subject: RE: [CMake] RE: CMake 2.4.1/VC71 Why the wierd project.dir
subdirs?
Also, is there are a way of recovering the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Trevor Kellaway
Sent: Friday, May 11, 2007 12:15 AM
To: cmake@cmake.org
Subject: RE: [CMake] RE: CMake 2.4.1/VC71 Why the wierd project.dir
subdirs?
Kishore,
Perhaps you could use
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Trevor Kellaway
Sent: Saturday, May 05, 2007 1:49 PM
To: cmake@cmake.org
Subject: RE: [CMake] Thoughts on Cross-compiling with CMake
Kishore,
OK. Personally, I use KDevelop and do not have first
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Neundorf
Sent: Monday, April 30, 2007 6:21 PM
To: cmake@cmake.org
Subject: Re: [CMake] Thoughts on Cross-compiling with CMake
main CVS tree (I use Subversion) and this forum, I assume
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Trevor Kellaway
Sent: Friday, May 04, 2007 6:14 PM
To: cmake@cmake.org
Subject: RE: [CMake] Thoughts on Cross-compiling with CMake
Hi,
It is really nice to know that there is now active
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Ajay Divekar
Sent: Thursday, April 19, 2007 10:04 PM
To: cmake@cmake.org
Subject: [CMake] CMake does not take gcc34 as its compiler
Hello,
I tried to run cmake using the cmake -i . command and
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Pascal Fleury
Sent: Wednesday, April 18, 2007 3:45 AM
To: cmake@cmake.org
Subject: Re: [CMake] Re: Avoiding convenience libs
On Tuesday 17 April 2007 23:55:44 Matthew Woehlke wrote:
WAG: variables
If I add the flag --register-prefix-optional cmake actually passes
-fregister-prefix-optional to the command line and this causes the
command to fail saying that the option does not exist.
How can I avoid this?
Warm regards,
Kishore
___
CMake mailing
]
Sent: Wednesday, April 04, 2007 7:02 PM
To: Kishore, Jonnalagadda (IE10)
Cc: cmake@cmake.org
Subject: Re: [CMake] --register-prefix-optional becomes
-fregister-prefix-
optional
Kishore, Jonnalagadda (IE10) wrote:
If I add the flag --register-prefix-optional cmake actually passes
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Matthew Woehlke
Sent: Wednesday, April 04, 2007 10:15 PM
To: cmake@cmake.org
Subject: [CMake] ELSEIF? ...is or is not implemented?
I found this:
KJI This would have worked just fine except that INCLUDE_DIRECTORIES
returns
KJI semicolon separated list of directory names not a space separated
list
Seems to be true for any list oft values as I experienced also. Is it
true content or only the formatting of the MESSAGE() command?
Kishore, Jonnalagadda (IE10) wrote:
KJI This would have worked just fine except that
INCLUDE_DIRECTORIES
returns
KJI semicolon separated list of directory names not a space
separated
list
Seems to be true for any list oft values as I experienced also. Is
it
true content or only
Is there a variable with all the compile options concatenated? A
variable with common CMAKE_C_FLAGS + CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
I am looking for this for passing them to the assembler macro where I
use ADD_CUSTOM_COMMAND.
What are
I would really appreciate anyone who can throw more light to explain the
role of the PROJECT command.
Here is why. I have a CMakeLists.txt in top level source tree and it
contains:
MESSAGE(CMAKE_C_LINK_EXECUTABLE = ${CMAKE_C_LINK_EXECUTABLE}
FLAGS = ${FLAGS}
Kishore, Jonnalagadda (IE10) wrote:
Is there a variable with all the compile options concatenated? A
variable with common CMAKE_C_FLAGS +
CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
I am looking for this for passing them to the assembler macro where
Kishore, Jonnalagadda (IE10) wrote:
Is there a variable with all the compile options concatenated? A
variable with common CMAKE_C_FLAGS +
CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
I am looking for this for passing them to the assembler
I have problems with ADD_DEFINITIONS : I have two target in my
CMakeLists which I'd like to have different -D flags. If I add
ADD_DEFINITIONS, it seems like both targets are affected. How coul I
do
such thing ?
You have two options.
1) Set target specific definitions using the command
Assembly files explicitly given as source files for a target are
completely ignored. From google searches, it seems to be a known
issue
and the solution lies with adding custom commands.
I am not familiar with adding custom commands. And thus have
assembly
files assembled before
Is it possible to set the prefix and suffix to lib and .a for all
libraries and .elf suffix to all executables?
As mentioned in an earlier mail, I am having trouble with the executable
trying to link to libraries with .lib suffix.
Warm regards,
Kishore
Assembly files explicitly given as source files for a target are
completely ignored. From google searches, it seems to be a known
issue
and the solution lies with adding custom commands.
I am not familiar with adding custom commands. And thus have
assembly
files assembled
Filipe Sousa wrote:
Kishore, Jonnalagadda (IE10) wrote:
Is it possible to set the prefix and suffix to lib and .a for
all
libraries and .elf suffix to all executables?
CMAKE_STATIC_LIBRARY_PREFIX
CMAKE_STATIC_LIBRARY_SUFFIX
CMAKE_SHARED_LIBRARY_PREFIX
CMAKE_SHARED_LIBRARY_SUFFIX
My setup:
Project/CMakeLists.txt:
ADD_SUBDIRECTORY(dir)
LINK_LIBRARIES(mylib)
ADD_EXECUTABLE(myexec main.c)
Project/dir/CMakeLists.txt:
ADD_LIBRARY(mylib lib.c)
SET_TARGET_PROPERTIES(mylib
PROPERTIES
On Tuesday 20 March 2007 07:07:35 Kishore, Jonnalagadda (IE10) wrote:
Kishore, Jonnalagadda (IE10) wrote:
This is now a little confusing especially, when the description says
automatically add CMAKE_CURRENT_SOURCE_DIR and
CMAKE_CURRENT_BINARY_DIR
to the include directories _in every
When and under what conditions are the cache variable read?
In the top level CMakeLists.txt of my project I have the following
lines;
IF(NOT ARCH)
MESSAGE(STATUS Setting ARCH to x86)
SET(ARCH x86 CACHE STRING
Choose the architecture, options are:
${SUPPORTED_ARCHS}
Assembly files explicitly given as source files for a target are
completely ignored. From google searches, it seems to be a known issue
and the solution lies with adding custom commands.
I am not familiar with adding custom commands. And thus have assembly
files assembled before building a
As I may have mentioned before, I am cross compiling and so far i seem
to be doing OK.
To enable cross compiling I have the macro
MACRO(ENABLE_CROSSCOMPILE)
SET (CMAKE_SKIP_COMPATIBILITY_TESTS 1)
SET (CMAKE_C_COMPILER_WORKS 1)
SET (CMAKE_CXX_COMPILER_WORKS 1)
SET
Assembly files explicitly given as source files for a target are
completely ignored. From google searches, it seems to be a known issue
and the solution lies with adding custom commands.
I am not familiar with adding custom commands. And thus have assembly
files assembled before building a
My setup:
Project/CMakeLists.txt:
ADD_SUBDIRECTORY(dir)
LINK_LIBRARIES(mylib)
ADD_EXECUTABLE(myexec main.c)
Project/dir/CMakeLists.txt:
ADD_LIBRARY(mylib lib.c)
SET_TARGET_PROPERTIES(mylib
PROPERTIES
PREFIX
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Kishore, Jonnalagadda (IE10)
Sent: Wednesday, March 21, 2007 1:28 AM
To: cmake@cmake.org
Subject: [CMake] LINK_LIBRARIES() does not respect SUFFIX/PREFIX
My setup:
Project/CMakeLists.txt
Thanks for your reply. I did read the wiki that basically said the
same
thing.
That's 'cuz I wrote it after it was posted here. :-)
That's funny! I am pretty sure I thought of using it after reading about
it on one of the pages... ;-)
I just checked again and confirm that the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Filipe Sousa
Sent: Friday, March 16, 2007 2:33 AM
To: cmake@cmake.org
Subject: Re: [CMake] CMAKE_INCLUDE_CURRENT_DIR?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kishore, Jonnalagadda (IE10
Can someone explain to me the use of CMAKE_INCLUDE_CURRENT_DIR?
In the root CMakeLists.txt file of my project I tried setting the
variable to ON (tried 1 as well) with:
SET(CMAKE_INCLUDE_CURRENT_DIR ON)
This seemed to make no difference. My expectation reading
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Trevor Kellaway
Sent: Sunday, March 04, 2007 10:39 PM
To: kitts; cmake@cmake.org
Subject: RE: [CMake] crosscompiling problems on XP
Kishore,
On Thursday 01 Mar 2007 IST, Kishore, Jonnalagadda (IE10) wrote
I have recently tried porting a project to CMake but I am facing a few issues
when cross-compiling
The project can be compiled with a varying set of compilers (already works with
our custom makefiles) and currently the only option seems to be passing this
information along with the cmake
37 matches
Mail list logo
