On 30.03.09 17:10:10, Allen Gooch wrote:
When I run it, the messages indicate that my FindExpat is being used,
instead of the one installed by cmake in
/usr/local/share/cmake-2.7/Modules/FindEXPAT.cmake, however my logging out
of the Expat_INCLUDE_DIR and Expat_LIBRARY values indicate that
In your toolchain file, what do you have
CMAKE_FIND_ROOT_PATH_MODE_INCLUDE set to? If it is set to ONLY, then
cmake will only look in the CMAKE_FIND_ROOT_PATH for boost, which is
probably set to $QNX_TARGET. Since you most likely don't have boost in
your $QNX_TARGET directory, findBoost will
Hi James,
Thanks for your reply. I'm going to comment on your remarks inline. But
first, let me explain what I wanted to accomplish.
My intention is to keep a list of valid CMake options so that I can
iterate over it. It would have been nice if CMake offered another way of
doing this, but I
Hi Bill,
Wouldn't it be better if CMake kept track of these variables internally.
I mean, usually the HAS_X variables are the result of calls to
check_include_file() and check_function_exists(). The Autotools handle
this under the hood.
CMake might keep a list of these variables, possibly one per
Dear CMake Community,
I have a project where there are:
LibraryA
LibraryB (depends on LibraryA)
Executable (depends on LibraryB and xml2)
during linking the order for link libraries is LibraryB -lxml2 LibraryA.
Should LibraryA (which is internal to the project) be specified before external
Hi Denis,
That doesn't really matter. What *does* matter is that libraries appear
in dependency order. I mean by that: if libA depends on libB, then
libB must appear after libA on the link line. But if libA does not
depend on, say libxml, than the order of these two libs is irrelevant.
Best
Hi all,
Could anyone shed a light on the following. IMHO it's a bug.
I'm running cmake version 2.6-patch 2.
Here's my initial CMakeLists.txt file:
cmake_minimum_required(VERSION 2.6)
set(options fine good bad)
option(fine Fine OFF)
option(good Good OFF)
option(bad Bad OFF)
foreach(opt
Hi again,
Would anybody have a solution for this?
Thanks
Alexandre
Sent: Monday, 30 March 2009 17:31
Hi,
I import some libs like this:
add_library(${name} ${type} IMPORTED)
set_target_properties(${name} PROPERTIES
2009/3/30 Alexander Neundorf a.neundorf-w...@gmx.net
On Monday 30 March 2009, Adolfo Rodríguez wrote:
Hi,
I have set up a toolchain file [1] to enable cross-compiling a project.
In
my current setup, both the host and target environments are
binary-compatible (both are x86 and are
Marcel Loose wrote:
Hi Bill,
Wouldn't it be better if CMake kept track of these variables internally.
I mean, usually the HAS_X variables are the result of calls to
check_include_file() and check_function_exists(). The Autotools handle
this under the hood.
CMake might keep a list of these
Hi Alexandre,
I don't think that CMake is able to handle this. I searched for a
solution to a similar problem involving the use of the --start-group and
--end-group option for ld on Linux. You might be able to define custom
rules for this, but then you are definitely on platform-dependent
ground.
Hi Martin,
Well, I came to this ugly platform-dependant workaround. I hate that,
but it works.
Example: Here, libC depends on libB which depends on libA. To surround
libB:
IMPORTED_LINK_INTERFACE_LIBRARIES for libB: -z defaultextract;libA
IMPORTED_LINK_INTERFACE_LIBRARIES for libC: -z
I think the better solution would be to have the various Find functions
(package, library, program) define a variable for that package to an internal
list - which is what I think Marcel might have been hinting at.
The user could add more variables to the same internal list.
So essentially:
#
I'm trying to use CPack to install a target at:
C:\Program Files\Vendor\Package
but it seems that CPack only allows me to do:
C:\Program Files\Package
Any ideas how to create that extra directory hierarchy?
TIA
/Rob
___
Powered by
According to CMake/Modules/NSIS.template.in : ;Default installation folder
InstallDir $programfil...@cpack_package_install_directory@
So set the variable CPACK_PACKAGE_INSTALL_DIRECTORY to be Vendor\Package
like this:
SET(CPACK_PACKAGE_INSTALL_DIRECTORY Vendor\\Package)
Then set the
Hi,
In my project, all sources named .c are C++ files, and should be
considered as CXX language files.
I tried to set this with CMAKE_LANG_SOURCE_FILE_EXTENSIONS, at the
very beginning of my project, without success. How should I do it?
cmake_minimum_required (VERSION 2.6)
Hello,
Try
SET_SOURCE_FILES_PROPERTIES( file1.c file2.c file3.c PROPERTIES LANGUAGE CXX )
On Tue, Mar 31, 2009 at 5:16 PM, Alexandre Feblot
alexandre.feb...@thomsonreuters.com wrote:
Hi,
In my project, all sources named .c are C++ files, and should be considered
as CXX language files.
On Tue, Mar 31, 2009 at 7:04 AM, BRM bm_witn...@yahoo.com wrote:
I think the better solution would be to have the various Find functions
(package, library, program) define a variable for that package to an
internal list - which is what I think Marcel might have been hinting at.
The user
I am trying to compile a mixed f90/C++ program linked with g++.
The fortran compiler flags don't seem to be automatically passed
through to the g++ linker.
For example, I want to do:
set( CMAKE_Fortran_FLAGS -fconvert=big-endian )
When I do this for a fortran program (linked with
James Bigler wrote:
If this feature comes to fruition, I would like the ability to specify
which flags make it into what header. In one project I worked on all
our configuration defines were in a single header. This caused
extremely long recompiles if something happened to change the one
Well, I indeed found this to work, but my project has about 2 c files.
Alin, forcing CC to a C++ compiler is not an option either, as I also have a
couple of libs which must be compiled with a C-ansi compiler.
I found that I could get the correct behaviour by modifying the value of
I want to use doxygen to generate documentation, but I also want it to only run
if something has changed. At first I was playing with the idea of having it be
dependent on all source header files, but I quickly realized that that would
be difficult or impossible in cmake. Then I realized
Hello,
Have you tried PROJECT( myproject CXX ) ?
On Tue, Mar 31, 2009 at 5:53 PM, Alexandre Feblot
alexandre.feb...@thomsonreuters.com wrote:
Well, I indeed found this to work, but my project has about 2 c files.
Alin, forcing CC to a C++ compiler is not an option either, as I also have a
Hi,
Should not the flag be passed to the linker? So in this case the linker flags
are read from the c++ compiler flags?
regards,
Alin
--
__
If the Universities will not study useless subjects, who will?
On Tue, Mar 31, 2009 at 5:53 PM, Alexandre Feblot
alexandre.feb...@thomsonreuters.com wrote:
Well, I indeed found this to work, but my project has about 2 c files.
Nice ! It this project called GNU/Linux ? ;)
Alin, forcing CC to a C++ compiler is not an option either, as I also have a
How about:
# Each variable can have a registered filter name - packages/programs/libraries
would use their name
cmake_autoheader_add_variable(has_some_other_package, filter_name)
# user controls what the output file is
# User can generate a C #define method (default method if no language
How about making it depend on the ALL target?
On Tue, Mar 31, 2009 at 6:07 PM, Lezz Giles lgi...@soapstonenetworks.comwrote:
I want to use doxygen to generate documentation, but I also want it to only
run if something has changed. At first I was playing with the idea of
having it be
CMake if commands are interesting in the sense that variable names can be
used directly. In most other languages you have to explicitly dereference
the variable to get the value out. I think when you use a string that is
the same name as a variable you are getting problems.
if(variable
BRM wrote:
How about:
# Each variable can have a registered filter name - packages/programs/libraries
would use their name
cmake_autoheader_add_variable(has_some_other_package, filter_name)
# user controls what the output file is
# User can generate a C #define method (default method if
Should not the flag be passed to the linker? So in this case the
linker flags are read from the c++ compiler flags?
I tried adding
add_definitions( ${CMAKE_Fortran_FLAGS} )
But the g++ linker complained about an unrecognized option (the -
fconvert=big-endian option).
When
On Tue, Mar 31, 2009 at 06:18:49PM +0200, Adolfo Rodríguez wrote:
How about making it depend on the ALL target?
I believe this will cause the doxygen target to be run every time, which
is not what the OP wants.
My first guess would be the ALL_TARGETS approach. Just make it part of
your coding
On Tue, Mar 31, 2009 at 9:45 AM, Bill Hoffman bill.hoff...@kitware.comwrote:
James Bigler wrote:
If this feature comes to fruition, I would like the ability to specify
which flags make it into what header. In one project I worked on all our
configuration defines were in a single header.
Hi,
g++ knows of -mbig-endian not -f
Anyhow is just a thought.
Alin
--
__
If the Universities will not study useless subjects, who will?
G. F. FitzGerald, Nature, 45/46, 392 (1892)
If you want to pass something to g++ linker, you should do this with
-Wl,--my-special-flag
Denis
Should not the flag be passed to the linker? So in
this case the linker flags are read from the c++ compiler
flags?
I tried adding
add_definitions( ${CMAKE_Fortran_FLAGS} )
But
I don't think I can make a custom command depend on ALL. Here's the relevant
CMakeLists.txt fragment that I have now...
ADD_EXECUTABLE( hellow hellow.c )
ADD_CUSTOM_COMMAND(OUTPUT ${CMAKE_BINARY_DIR}/docs COMMAND cat
${CMAKE_SOURCE_DIR}/hellowdoc.template ${CMAKE_BINARY_DIR}/docs)
Hi All,
I am trying to build a project containing several subprojects that are
included via add_subdirectory. Now, here is an example demonstrating
the problem:
The test project contains the following CMakeLists.txt:
project( CMakeTest )
cmake_minimum_required( VERSION 2.6 )
Yes, my solution does have a more global variable list. However, I think that
in this case it works to your advantage as you only have to build the list once
and no one has to explicitly know about each list. This makes using a find
function (e.g. FindQt()) easier to write - it just has append
David Cole skrev:
(The CPACK_NSIS_DISPLAY_NAME variable defaults to the same
as CPACK_PACKAGE_INSTALL_DIRECTORY, but you probably don't want the
Vendor\\ in the display name, which is used elsewhere in
NSIS.template.in http://NSIS.template.in.)
Thanx, but it doesn't work as expected,
How would this global auto header stuff work with two sub projects both
wanting to do auto headers?
Do they share one header, or do they get their own? If they share, what
if they both want a different name for the header file?
Clint
BRM wrote:
Yes, my solution does have a more global
g++ knows of -mbig-endian not -f
g++ --help -v provides no information on any endian operations.___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
Let me try this again.
I have a f90 subroutine that performs file IO. I would like to link
that with a C++ driver.
If I use a fortran driver, I am able to set the binary format via
set( CMAKE_Fortran_FLAGS -fconvert=big-endian )
This results in file IO in big-endian format.
When
What is the xcode generator name on the command line? I don't see it
in the official
list of
generatorshttp://cmake.org/cmake/help/cmake2.6docs.html#section_Generators
.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
It's name is Xcode and it's only available on the Mac build of CMake.
On Tue, Mar 31, 2009 at 2:33 PM, Robert Dailey rcdai...@gmail.com wrote:
What is the xcode generator name on the command line? I don't see it in the
official list of
(And the official list you pointed to is generated by a Windows build of
CMake)
On Tue, Mar 31, 2009 at 2:34 PM, David Cole david.c...@kitware.com wrote:
It's name is Xcode and it's only available on the Mac build of CMake.
On Tue, Mar 31, 2009 at 2:33 PM, Robert Dailey rcdai...@gmail.com
Am Dienstag 31 März 2009 19:48:49 schrieb Tobias Rudolph:
add_library( iLib SHARED IMPORTED )
set_target_properties( iLib PROPERTIES IMPORTED_LOCATION /opt/local/
lib/libzip.dylib )
add_library( libFoo SHARED foo.cpp )
target_link_libraries( libFoo iLib )
According to the
Thanks David.
Where can I find a platform-ambiguous version of the documentation then?
On Tue, Mar 31, 2009 at 1:35 PM, David Cole david.c...@kitware.com wrote:
(And the official list you pointed to is generated by a Windows build of
CMake)
On Tue, Mar 31, 2009 at 2:34 PM, David Cole
Notice my original API suggestion - the project controls its own header - just
not the list of available items.
So essentially:
1) Cmake runs, finds packages, builds list
2) user add extra items to list
3) header generated
Noting from my original API example:
cmake_autoheader(C,
man g++
add_definition is a preprocessor directive not linking flag
Alin
--
__
If the Universities will not study useless subjects, who will?
G. F. FitzGerald, Nature, 45/46, 392 (1892)
Robert Dailey wrote:
Thanks David.
Where can I find a platform-ambiguous version of the documentation then?
There really is not any for this...
cmake --help
Will give you the generators available for your particular cmake.
-Bill
___
Powered by
On Tuesday 31 March 2009, BRM wrote:
I think the better solution would be to have the various Find functions
(package, library, program) define a variable for that package to an
internal list - which is what I think Marcel might have been hinting at.
Something similar exists for FIND_PACKAGE()
On Tuesday 31 March 2009, Bill Hoffman wrote:
Marcel Loose wrote:
Hi Bill,
Wouldn't it be better if CMake kept track of these variables internally.
I mean, usually the HAS_X variables are the result of calls to
check_include_file() and check_function_exists(). The Autotools handle
On Tuesday 31 March 2009, James Bigler wrote:
...
Why not something similar to what you proposed, but without the
intermediate configure.h.in step and being able to specify comments and
perhaps custom strings. You could also specify things multiple kinds and
they all just get inserted one
On Tuesday 31 March 2009, Adolfo Rodríguez wrote:
2009/3/30 Alexander Neundorf a.neundorf-w...@gmx.net
...
[1] In case you think it helps, these are my rpath settings:
# Use, i.e. don't skip the full RPATH for the build tree
set(CMAKE_SKIP_BUILD_RPATH FALSE)
# When building, don't use the
I have the following macro for generation of c++ source from a proprietary
IDL language:
macro (oidl_generate IDL_SOURCES IDL_INCLUDE_DIRS)
message (STATUS IDL Sources: ${IDL_SOURCES})
foreach (idlsrc ${IDL_SOURCES})
get_filename_component (idlsrc_file ${idlsrc} NAME_WE)
On Tue, Mar 31, 2009 at 12:47:33PM -0400, Lezz Giles wrote:
ADD_EXECUTABLE( hellow hellow.c )
ADD_CUSTOM_COMMAND(OUTPUT ${CMAKE_BINARY_DIR}/docs COMMAND cat
${CMAKE_SOURCE_DIR}/hellowdoc.template ${CMAKE_BINARY_DIR}/docs)
ADD_CUSTOM_TARGET(documentation DEPENDS ${CMAKE_BINARY_DIR}/docs)
Hello,
I am the developer of PyTrilinos, the python interface to Trilinos and
I have hit upon some unexpected behavior.
I am trying to wrap the interface to NOX, which utilizes nested
namespaces. I shadow this structure in python by utilizing nested
modules. For example, a subset of
So I want to collect a list of targets which I'll use in a central
CMakeLists.txt. My files are arranged like this:
Project CMakeLists.txt
-Central CMakeLists.txt file which pulls in
o src/CMakeLists.txt
o tst/CMakeLists.txt
-Central CMakeLists.txt file then defines a
On Mar 31, 2009, at 21:10, Hendrik Sattler wrote:
Am Dienstag 31 März 2009 19:48:49 schrieb Tobias Rudolph:
add_library( iLib SHARED IMPORTED )
set_target_properties( iLib PROPERTIES IMPORTED_LOCATION /opt/local/
lib/libzip.dylib )
add_library( libFoo SHARED foo.cpp )
On Tue, Mar 31, 2009 at 2:06 PM, Allen Gooch allen.go...@gmail.com wrote:
I have the following macro for generation of c++ source from a proprietary
IDL language:
macro (oidl_generate IDL_SOURCES IDL_INCLUDE_DIRS)
message (STATUS IDL Sources: ${IDL_SOURCES})
foreach (idlsrc
On Tue, Mar 31, 2009 at 2:50 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Tue, Mar 31, 2009 at 04:47:23PM -0400, Lezz Giles wrote:
What I want to do is pass values up from src/CMakeLists.txt and
tst/CMakeLists.txt that can be used in the custom_command. A normal
variable doesn't work - the
Alin,
Thank you for your patience. I now have this set via
set( CMAKE_EXE_LINKER_FLAGS -mbig-endian )
However, this does not seem to affect the reading of the big-endian
binary file (which is in read in fortran). Perhaps I am still not
setting it properly?
James
On Mar 31,
Mostly to fix the issue with Visual Studio and header files that was
introduced with CMake 2.6.3, I am working on 2.6.4. I have a release
candidate RC 3 that can be found here:
http://www.cmake.org/files/v2.6
Other changes in 2.6.4 are as follows:
Changes in CMake 2.6.4 RC 3
- Documentation
On Tue, Mar 31, 2009 at 6:13 PM, James Bigler jamesbig...@gmail.com wrote:
I just recently discovered another way to do this. I was troubled that
pushing it up to the parent scope only pushes it up one level, so if you
want to push a variable up to the top, you must push it at each level in
On Mar 31, 2009, at 8:46 PM, Philip Lowman phi...@yhbt.com wrote:
On Tue, Mar 31, 2009 at 6:13 PM, James Bigler
jamesbig...@gmail.com wrote:
I just recently discovered another way to do this. I was troubled
that pushing it up to the parent scope only pushes it up one level,
so if you want
On Tue, Mar 31, 2009 at 3:27 PM, BRM bm_witn...@yahoo.com wrote:
Notice my original API suggestion - the project controls its own header -
just not the list of available items.
So essentially:
1) Cmake runs, finds packages, builds list
2) user add extra items to list
3) header generated
On Tue, Mar 31, 2009 at 12:23 AM, James Bigler jamesbig...@gmail.comwrote:
I think he wants to run ccmake and configure things how he likes and then
get a command line that would produce the equivalent configuration without
ccmake (i.e. cmake -DSOMEVAR:BOOL=ON
By changing NSIS.template.in to use CPACK_NSIS_DISPLAY_NAME instead as
Name for the
installation, it works fine.
Actually I see now that this is bug
(http://public.kitware.com/Bug/view.php?id=8682)
/R
___
Powered by www.kitware.com
Visit other
67 matches
Mail list logo
