Re: [cmake-developers] GenerateExportHeader macro in CMake?
On Thu, Aug 11, 2011 at 11:30 AM, Stephen Kelly steve...@gmail.com wrote: David Cole wrote: Stephen, Welcome to CMake development :-) Thanks :), Brad and I are both fairly busy this week. Please continue making fixes and merging them into 'next' for dashboard testing as you are able. You're getting closer. It looks like you already made a similar change to what Bill was asking us to push...? Yep, I pushed a similar change to that, and it passed in the continuous build already. Let me know if you would like me to try anything on a specific machine here at Kitware for you. I have access to all the Kitware dashboard machines, and even some of the non-Kitware dashboard machines. Thanks for your effort... We've all been there when adding something brand new into CMake. I think it will be mostly green again tomorrow in the nightlies. I think the deprecated attributes are excluded a bit too pessimistically at the moment, but I'll wait until it's all green before messing around with that. Keep up the good work! Thanks :), Steve. David Cole Kitware, Inc. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Hi Stephen, So... this topic is in 'next', and today, it only fails on 4 dashboards in total. I will try to get output for you on the wcl (Watcom) compiler dashboard -- since it timed out, there is no test output reported on CDash... http://www.cdash.org/CDash/testSummary.php?project=1name=Module.GenerateExportHeaderdate=2011-08-23 Can you take a look at the CDash output of the other platforms where this test is still failing, and recommend changes that might eliminate all the test failures? We can't really merge this to 'master' and include it in the upcoming CMake 2.8.6 until we've resolved, worked-around or avoided the test failures on the remaining dashboard submissions. Thanks, David Cole Kitware, Inc. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] GenerateExportHeader macro in CMake?
David Cole wrote: Hi Stephen, So... this topic is in 'next', and today, it only fails on 4 dashboards in total. I will try to get output for you on the wcl (Watcom) compiler dashboard -- since it timed out, there is no test output reported on CDash... http://www.cdash.org/CDash/testSummary.php?project=1name=Module.GenerateExportHeaderdate=2011-08-23 Can you take a look at the CDash output of the other platforms where this test is still failing, and recommend changes that might eliminate all the test failures? Yep, I've just had a look and possibily fixed the Intel and HPUX cases. The AIX one fails because the visibility test passes, because check_cxx_compiler_flag does not have a FAIL_REGEX for its warning: http://www.cdash.org/CDash/testDetails.php?test=109778717build=1458523 http://www.cdash.org/CDash/testDetails.php?test=110283056build=1458523 I've also pushed a possible fix for that to check_cxx_compiler_flag on the branch. The CentOS machine seems to have problems unrelated to this test: http://www.cdash.org/CDash/testDetails.php?test=109887854build=1457339 http://www.cdash.org/CDash/viewTest.php?buildid=1457339 All have ' undefined reference to `_Unwind_Resume'' in their output. That only leaves Watcom as you say, and I've just tried to simplify the tests for that compiler. If the timeouts persist, I can start just disabling some tests for that compiler. We can't really merge this to 'master' and include it in the upcoming CMake 2.8.6 until we've resolved, worked-around or avoided the test failures on the remaining dashboard submissions. Hopefully that will be resolved in the next few days then :) Thanks, Steve. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] Error running link command: Bus error
Looks like a linker error not a cmake one. You could run make VERBOSE=1 in order to see the command which is failing. The terminal output of Tutorial/Step2 is: --- mac151:mac32 gmp$ make VERBOSE=1 /Applications/CMake 2.8-5.app/Contents/bin/cmake -H/Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2 -B/Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32 --check-build-system CMakeFiles/Makefile.cmake 0 /Applications/CMake 2.8-5.app/Contents/bin/cmake -E cmake_progress_start /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/CMakeFiles /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make -f MathFunctions/CMakeFiles/MathFunctions.dir/build.make MathFunctions/CMakeFiles/MathFunctions.dir/depend cd /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32 /Applications/CMake 2.8-5.app/Contents/bin/cmake -E cmake_depends Unix Makefiles /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2 /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/MathFunctions /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32 /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions/CMakeFiles/MathFunctions.dir/DependInfo.cmake --color= Dependee /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions/CMakeFiles/MathFunctions.dir/DependInfo.cmake is newer than depender /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions/CMakeFiles/MathFunctions.dir/depend.internal. Dependee /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions/CMakeFiles/CMakeDirectoryInformation.cmake is newer than depender /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions/CMakeFiles/MathFunctions.dir/depend.internal. Scanning dependencies of target MathFunctions make -f MathFunctions/CMakeFiles/MathFunctions.dir/build.make MathFunctions/CMakeFiles/MathFunctions.dir/build /Applications/CMake 2.8-5.app/Contents/bin/cmake -E cmake_progress_report /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/CMakeFiles 1 [ 50%] Building CXX object MathFunctions/CMakeFiles/MathFunctions.dir/mysqrt.cxx.o cd /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions /usr/bin/c++ -I/Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32 -I/Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/MathFunctions -o CMakeFiles/MathFunctions.dir/mysqrt.cxx.o -c /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/MathFunctions/mysqrt.cxx Linking CXX static library libMathFunctions.a cd /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions /Applications/CMake 2.8-5.app/Contents/bin/cmake -P CMakeFiles/MathFunctions.dir/cmake_clean_target.cmake cd /Volumes/amm-er/gmp/Projects/_shared/cmake_unixMakefile_testProject/Tutorial/Step2/mac32/MathFunctions /Applications/CMake 2.8-5.app/Contents/bin/cmake -E cmake_link_script CMakeFiles/MathFunctions.dir/link.txt --verbose=1 /usr/bin/ar cr libMathFunctions.a CMakeFiles/MathFunctions.dir/mysqrt.cxx.o /usr/bin/ranlib libMathFunctions.a Error running link command: Bus error make[2]: *** [MathFunctions/libMathFunctions.a] Error 1 make[1]: *** [MathFunctions/CMakeFiles/MathFunctions.dir/all] Error 2 make: *** [all] Error 2 --- When I do that with the project I originally want to build, the output is: --- [ ... compilation output of some files ... ] Linking C static library libutillib.a /Applications/CMake 2.8-5.app/Contents/bin/cmake -P CMakeFiles/utillib.dir/cmake_clean_target.cmake /Applications/CMake 2.8-5.app/Contents/bin/cmake -E cmake_link_script CMakeFiles/utillib.dir/link.txt --verbose=1 /usr/bin/ar cr libutillib.a CMakeFiles/utillib.dir/src/deb_dum.c.o CMakeFiles/utillib.dir/src/deb_out.c.o CMakeFiles/utillib.dir/src/errorhnd.c.o CMakeFiles/utillib.dir/src/matrixCalloc.c.o CMakeFiles/utillib.dir/src/mlfile.c.o CMakeFiles/utillib.dir/src/ngsalloc.c.o CMakeFiles/utillib.dir/src/uci.c.o CMakeFiles/utillib.dir/src/util_inf.c.o /usr/bin/ranlib libutillib.a Error running link command: Bus error make[2]: *** [libutillib.a] Error 1 make[1]: *** [CMakeFiles/utillib.dir/all] Error 2 make: *** [all] Error 2 --- Does the same project work on a another platform like some linux box? (using
[CMake] configuration based add_custom_command
I'm trying to setup a custom command to be executed during Release build only (Xcode) using CMake 2.8.4, but I cannot find any configuration based options to ADD_CUSTOM_COMMAND ? Workarounds ? TIA /Rob ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] configuration based add_custom_command
On Tue 23 Aug 2011 11:21:07 AM CEST, Robert Bielik wrote:
I'm trying to setup a custom command to be executed during Release build
only (Xcode) using CMake 2.8.4, but I cannot find
any configuration based options to ADD_CUSTOM_COMMAND ? Workarounds ?
TIA
/Rob
The easiest way around this I can see is to wrap the command in a
CMake-script like this:
add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/someFile.txt
COMMAND ${CMAKE_COMMAND}
-DCONFIG=$CONFIGURATION
-DOUTPUT=${CMAKE_CURRENT_BINARY_DIR}/someFile.txt
-P ${CMAKE_SOURCE_DIR}/generateSomeFile.cmake
DEPENDS ${CMAKE_SOURCE_DIR}/generateSomeFile.cmake
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
COMMENT Generating someFile.txt
VERBATIM)
And then, inside the generateSomeFile.cmake wrapper file you do:
if(CONFIG STREQUAL Release)
execute_process(COMMAND ...)
endif()
HTH
Michael
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Error running link command: Bus error
What is your environment like? The Tutorial steps run on all of our CMake dashboards, and we have several Unix Makefiles dashboards running on various Macs. We do not see this error anywhere... Mac Hardware: Model Name: Mac mini Model Identifier: Macmini4,1 Processor Name: Intel Core 2 Duo Processor Speed: 2,66 GHz Number Of Processors: 1 Total Number Of Cores:2 L2 Cache: 3 MB Memory: 8 GB Bus Speed:1,07 GHz Boot ROM Version: MM41.0042.B00 Mac Software: System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 Boot Volume: Macintosh HD Boot Mode:Normal Computer Name:mac151 Secure Virtual Memory:Not Enabled 64-bit Kernel and Extensions: No CMake Version 2.8.5 Do you have CC and/or CXX set to something? I used the Tutorial/Step2/CMakeLists.txt without modifying it. For my own project, I didn't set CC or CXX in my CMakeLists.txt file. Do you have a non-traditional or self-built compiler installed in your environment? No. MacPorts / Fink / some other non-Apple compiler? [...] I use Fink, and downloaded some libraries, but I didn't download/install a compiler intentionally via Fink. (And what version of Xcode and Mac OS X?) I use Xcode 4. Developer Information: Version: 4.0 (4A2002a) Location: /Developer Applications: Xcode:4.0.2 (99) Instruments: 4.0 (3538) Dashcode: 3.0.2 (333) SDKs: Mac OS X: 10.6: (4A2002a) iPhone OS: 4.3: (8H7) iPhone Simulator: 3.2: (7W367a) 4.0: (8A400) 4.1: (8B117) 4.2: (8C134) 4.3: (8H7) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] [CMAKE] Problem when moving an executable with a shared library
Hello CMake Experts! I don't know if it's here that I have to ask, so if I'm wrong, please tell me. I'm having a problem with CMake. Let me explain: I use CMake to build a program and a shared library (let me say, hello and libhello.so). When I use them from my build folder (if the folder with the source is /tmp/hello, the folder with the build is /tmp/hello/build), they work perfectly. But if I move them to another folder (like to /home/Renato ), hello does not run, unless if i put the libhello.so in the folder /tmp/hello/build. I wanted to make the hello executable to look at the same folder to where it is, not to the /tmp/hello/build folder, which doesn't change. How can I make that? And I have another question. I used the CPack and it stopped making the binary package at the middle of the process, running like this: - Run CPack packaging tool... CPack: Create package using STGZ CPack: Install projects CPack: - Run preinstall target for: hello CPack: - Install project: hello CPack: Create package CPack: - package: /home/renato/devel/CMakeTest/ build/hello-0.1.1-Linux.sh http://hello-0.1.1-linux.sh/ generated. CPack: Create package using TBZ2 CPack: Install projects CPack: - Run preinstall target for: hello CPack: - Install project: hello CPack: Create package CPack: - package: /home/renato/devel/CMakeTest/build/hello-0.1.1-Linux.tar.bz2 generated. - It does not add the files to the package, so it becomes a empty package, which does not have any file? How can I solve that too? I don't know if it matters, but here's my CMakeLists.txt: - CMAKE_MINIMUM_REQUIRED(VERSION 2.8) INCLUDE(InstallRequiredSystemLibraries) PROJECT(hello C) OPTION(USE_SHARED_LIBRARY Use a Shared Library OFF) IF(USE_SHARED_LIBRARY) ADD_LIBRARY(hellolib SHARED hellolib.c) ELSE(USE_SHARED_LIBRARY) ADD_LIBRARY(hellolib STATIC hellolib.c) ENDIF(USE_SHARED_LIBRARY) ADD_EXECUTABLE(hello hello.c) TARGET_LINK_LIBRARIES(hello hellolib) INCLUDE(CPack) - Thanks to everyone! ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] [CPACK] CPack not working properly
Hello CMake Experts! I don't know if it's here that I have to ask, so if I'm wrong, please tell me. I used the CPack and it stopped making the binary package at the middle of the process, running like this: - Run CPack packaging tool... CPack: Create package using STGZ CPack: Install projects CPack: - Run preinstall target for: hello CPack: - Install project: hello CPack: Create package CPack: - package: /home/renato/devel/CMakeTest/ build/hello-0.1.1-Linux.sh http://hello-0.1.1-linux.sh/ generated. CPack: Create package using TBZ2 CPack: Install projects CPack: - Run preinstall target for: hello CPack: - Install project: hello CPack: Create package CPack: - package: /home/renato/devel/CMakeTest/build/hello-0.1.1-Linux.tar.bz2 generated. - It does not add the files to the package, so it becomes a empty package, which does not have any file? How can I solve that too? I don't know if it matters, but here's my CMakeLists.txt: - CMAKE_MINIMUM_REQUIRED(VERSION 2.8) INCLUDE(InstallRequiredSystemLibraries) PROJECT(hello C) OPTION(USE_SHARED_LIBRARY Use a Shared Library OFF) IF(USE_SHARED_LIBRARY) ADD_LIBRARY(hellolib SHARED hellolib.c) ELSE(USE_SHARED_LIBRARY) ADD_LIBRARY(hellolib STATIC hellolib.c) ENDIF(USE_SHARED_LIBRARY) ADD_EXECUTABLE(hello hello.c) TARGET_LINK_LIBRARIES(hello hellolib) INCLUDE(CPack) - Thanks to everyone! ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Call for community dashboard submissions
On Tue, Aug 16, 2011 at 8:34 AM, Rolf Eike Beer e...@sf-mail.de wrote: Good morning, CMake-ers... Some gloomy news for some of our platforms (Sun, QNX): [...] - is there anybody else out there that could offer Continuous and Nightly dashboards for the QNX platform? I can't, but getting this is actually not very problematic. QNX offers a developer program that is free of charge and allows download of their software. This stuff runs pretty ok at least on Linux/KVM, likely also in other virtualization environments. So all this should be solvable without any additional hardware (as needed for the Sun stuff). The only thing that you have to live with is that it is sometimes creepingly slow and QNX 6.5 has a know bug on booting that randomly prevents it from proper starting on KVM. Trying again is enough there to get it eventually boot. If someone is willing to do this I would offer to add a helping hand every now and then. Ideally this would be a machine inside Kitware to make sure it's continued availability... Eike ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Does anybody have any further input on this thread? Any volunteers to submit a dashboard on Sun or QNX platforms? I don't think the ideal QNX machine resides inside Kitware, because we do not have any direct connection to that platform for any of our projects (to the best of my knowledge...) I think ideally, folks who rely on using CMake on the QNX platform and have decent platform knowledge would be better suited to keeping a CMake dashboard submission going into the future. Thanks, David Cole Kitware, Inc. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ok guys, why is configure_file() so sucky?
On Wednesday 17 August 2011, David Cole wrote:
On Wed, Aug 17, 2011 at 10:32 AM, Bill Hoffman bill.hoff...@kitware.com
wrote:
On 8/17/2011 10:17 AM, Andreas Mohr wrote:
[cue maximally inflammatory subject ;)]
Hi,
I keep encountering template file processing where
@VAR@ replacements end up empty due to the required template
variable simply not having been set (or empty) [or renamed away].
Doh.
I'd strongly vote for configure_file() to fail hard in such cases,
_by default_.
Build system life is already hard enough without all those nice
features of incomplete/insufficient commands (especially in the
packaging area I seem to keep hitting more holes
than actual functionality :-P).
So:
- change configure_file() behaviour to fail a CMake configure run hard
in case of unavailable (_not_ empty) @var@ (and perhaps ${var}?),
and have this be the _default_ setting
- add configure_file() flag to optionally _disable_ this hard failure
in case it's actually unwanted
- add configure_file() flag to optionally enable hard failure for the
other case of existing yet empty variables, too
- add policy around this new highly useful feature
- hmm, but these things {w|sh}ould apply to both ${xx} and @xx@ - do we
need
to have some configuration to tell behaviour apart?
- anything I've missed that should be added/changed for a more suitable
implementation?
- add these things to a new bug# for implementation
Done Deal?
far from... :)
If you did that, I am guessing, almost any cmake project using
configure_file would hard fail. Many projects use empty as a value. This
is a huge backwards compatibility can of worms... :)
...
We could do it without a policy and without a can of worms if we
simply add a new command instead of trying to re-use the existing,
perfectly reasonable configure_file command.
Or... by defaulting to the existing behavior and requiring the use of
a new flag to configure_file or setting a variable to indicate the new
STRICT behavior. (I assume you'd be more in favor of a new command
since you said you want this to happen by default.)
I'd vote against a new command. It would be mostly the same as
configure_file(), with only a small change.
One of the main problems with flagging empty variables as empty is
that sometimes you intend a variable to be empty... So really, only an
undefined variable should be considered an error.
Yes, I think so too.
Having a variable empty should be fine.
With a policy to fail if a configured variable is not defined, this should be
safe, shouldn't it ?
An option @FATAL_ERROR or @FAIL_ON_UNDEFINED would be also safe, but I doubt
many projects will go through their files and add that everywhere.
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CDT4 generator: source path configured incorrectly
On Wednesday 17 August 2011, Simon Barner wrote: Dear list, I use CMake 2.8.5 to generate Eclipse CDT4 projects (Eclipse Helios SR2 for C/C++ developers, CDT with mingw makefiles) on Windows 7 (32 bit). Since 2.8.5, for each project that is added using add_subdirectory(), a linked resource is created which enables me to easily navigate to files of subprojects. However, the source path for my linked subproject seems to be incorrect since I get the following warnings (see below for a test case). Please create an entry in the cmake bug tracker at http://public.kitware.com/Bug Alex ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] RPATH/RUNPATH
On Friday 19 August 2011, Michael Hertling wrote:
On 08/17/2011 10:03 PM, Knox, Kent wrote:
Yes, that's right. I'm currently using cmake with RPATH, but from what
I've been reading the RUNPATH header is now the more preferred approach.
If the user does not set LD_LIBRARY_PATH, the RUNPATH header should
take effect, but if the user DOES wish to overload your libraries, they
can go ahead and set LD_LIBRARY_PATH themselves assuming that they know
what they are doing.
This would help in our testing, as my RPATH settings have screwed up a
few of my testers as they thought they were shuffling libraries around,
but in fact my RPATH silently made their efforts for naught.
Thank you for the suggestion on modifying the linker flags myself; that
sounds feasible. I had also thought of running the 'chrpath'
http://linux.die.net/man/1/chrpath utility as a post-processing step
on my executables to manually change RPATH's into RUNPATH's, but I'm not
quite sure how to write this in CMake yet. Wanted to check first if
CMake had undocumented or planned settings first.
Kent
In order to enable ELF's DT_RUNPATH tag, you just need to set the
linker's --enable-new-dtags option, e.g. as in the following
exemplary project, provided you use GNU binutils' ld:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(RUNPATH C)
SET(CMAKE_VERBOSE_MAKEFILE ON)
SET(CMAKE_INSTALL_RPATH $ENV{HOME}/lib)
FILE(WRITE ${CMAKE_BINARY_DIR}/main.c int main(void){return 0;}\n)
ADD_EXECUTABLE(main main.c)
INSTALL(TARGETS main RUNTIME DESTINATION bin)
SET(CMAKE_EXE_LINKER_FLAGS -Wl,--enable-new-dtags)
In this way, the DT_RPATH tag in the final binary is duplicated for
DT_RUNPATH, and as the former is ignored when the latter is present,
it should suit your needs. Furthermore, CMake's rpath machinery can
operate as usual and the built-in ELF editor addresses the DT_RPATH
and DT_RUNPATH tags, so there is no necessity to have CMake handle
the DT_RUNPATH explicitly, in particular as ld does not provide an
immediate option to set this tag, AFAIK.
Can you please add that to the RPATH cmake wiki page ?
Thanks
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake and NaCl (Google NativeClient)
On Thursday 11 August 2011, Nils Hjelte wrote: Hello! I'm trying to port a C++ project to NaCl (http://code.google.com/chrome/nativeclient/), with cmake as the build system, and I need to figure out some things. I am using a Mac as build machine. I have changed the CMAKE_CXX_COMPILER/LINKER variables to use the nacl toolchain. What I would like to know is if it is possible to discard all the default compiler flags. I get lots of flags that the nacl compiler does not like, After a very quick first look, maybe this should be treated as cross compiling, with the target OS being NaCl or something like that. That way you'll have a platform file, where you can set all the flags as necessary for that target. Alex ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] GraphViz module?
Hi all, I was wondering if there is a GraphViz module that is included with cmake. I'm using an older 2.8.2 and can't seem to find such a module and I'm wondering if my installation is just missing it. I looked at the recent cmake docs and it seems that it doesn't exist? I did a search and came across this as one of my top hits: http://trac.mi.fu-berlin.de/seqan/browser/trunk/seqan/util/cmake/FindGraphviz.cmake Seems that it isn't officially part of cmake? Thank you! Ray PS: I realize that there is no reason why cmake has to have a graphviz module; but since there is a --graphviz argument to cmake, I thought there ought to be a FindGraphviz.cmake somewhere too and maybe I'm just missing it. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] masm msvc
Hi,
On Monday 15 August 2011, Micha Renner wrote:
This script...
# Copy paste from CMake Wiki
# Works only if CMake runs in the Visual Studio DOS Window
SET(MASMFound FALSE)
# test whether it is a x86 machine and masm is available
IF(${CMAKE_SYSTEM_PROCESSOR} MATCHES x86)
ENABLE_LANGUAGE(ASM_MASM)
IF(CMAKE_ASM_MASM_COMPILER_WORKS)
SET(MASMFound TRUE)
ENDIF(CMAKE_ASM_MASM_COMPILER_WORKS)
ENDIF(${CMAKE_SYSTEM_PROCESSOR} MATCHES x86)
# no assembler found
IF(NOT MASMFound)
MESSAGE(STATUS NOT)
ENDIF(NOT MASMFound)
...generates still the message:
The ASM_MASM compiler identification is unknown --!
Found assembler: C:/Program Files/Microsoft Visual Studio
10.0/VC/bin/ml.exe
How does your CMakeLists.txt look like ?
Please create an entry in the cmake bug tracker at
http://public.kitware.com/Bug
Please try to create a small example which you can attach there which
reproduces the problem.
Which version of cmake are you using ?
Which generator ?
ASM is currently only supported for the makefile-based generators, some
special support still has to be added for VisualStudio, I don't know about
Xcode.
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [CPACK] CPack not working properly
2011/8/23 Renato Utsch renatout...@gmail.com: Hello CMake Experts! I don't know if it's here that I have to ask, so if I'm wrong, please tell me. I used the CPack and it stopped making the binary package at the middle of the process, running like this: From the trace you gave it does not stopped it goes right to the end...but... - Run CPack packaging tool... CPack: Create package using STGZ CPack: Install projects CPack: - Run preinstall target for: hello CPack: - Install project: hello CPack: Create package CPack: - package: /home/renato/devel/CMakeTest/ build/hello-0.1.1-Linux.sh generated. CPack: Create package using TBZ2 CPack: Install projects CPack: - Run preinstall target for: hello CPack: - Install project: hello CPack: Create package CPack: - package: /home/renato/devel/CMakeTest/build/hello-0.1.1-Linux.tar.bz2 generated. - It does not add the files to the package, so it becomes a empty package, which does not have any file? How can I solve that too? Because may be you didn't installed anything in your project. I don't know if it matters, but here's my CMakeLists.txt: It does...keep reading... - CMAKE_MINIMUM_REQUIRED(VERSION 2.8) INCLUDE(InstallRequiredSystemLibraries) PROJECT(hello C) OPTION(USE_SHARED_LIBRARY Use a Shared Library OFF) IF(USE_SHARED_LIBRARY) ADD_LIBRARY(hellolib SHARED hellolib.c) ELSE(USE_SHARED_LIBRARY) ADD_LIBRARY(hellolib STATIC hellolib.c) ENDIF(USE_SHARED_LIBRARY) ADD_EXECUTABLE(hello hello.c) TARGET_LINK_LIBRARIES(hello hellolib) You miss at least one install rule per target you want to install. INSTALL(TARGETS hello hellolib RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE DESTINATION lib/static) INCLUDE(CPack) - Thanks to everyone! CPack will only put in a package the targets/files/directories which are INSTALLed by you CMakeLists.txt. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Using name other than CMakeLists.txt
Hi, Our multi-physics project depends on product build systems using both stock CMake 2.8.x and an incompatible fork of CMake which also (re)uses the CMake standard project filename (CMakeLists.txt). We need the ability to build this code base with both stock CMake and the CMake fork. We recognize the potential problems with this arrangement but we need to support both of these build capabilities for a while. I'd like to propose a patch that would replace all character literal occurrences of CMakeLists.txt in the CMake source code base with a variable that defaults to CMakeLists.txt, but permit that variable to be configured to a different name when running CMake. This would allow, for example, our project to contain both stock CMakeLists.txt files as well as other CMake project files such as CMakeLists.Trilinos. We could then configure this project with the Trilinos CMake build variant by running CMake like this: cmake -D CMAKE_PROJECT_FILENAME=CMakeLists.Trilinos ... where CMAKE_PROJECT_FILENAME is the new CMake variable. We've found this capability useful for our code coupling environment permitting use of a new CMake build variant while retaining use of the stock CMake build. Is there any interest in adding this capability to CMake? -- Noel Belcourt ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v2.8.5-1683-g2980df2
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 2980df20a6a19cf83dffecffd8bf2b997c086ac1 (commit)
via 1c2508a569da51041db7345e0c9eb41aa6aaefd9 (commit)
via d1795002956f8da746077fffb1c2aa0262063db2 (commit)
via 4fd1e28495e09af154f361602d30a0c5fc998ff4 (commit)
via 20980ef56a847fec7922983257fd5be467b689bd (commit)
via fe46e7e4866bd1a7678e1381da02df8c9f533aa0 (commit)
via 29b285c6a1b583f56257f3ca8113d6ce29f5d8d6 (commit)
via 3848b397ef6cae97ca28826582c0567cbe5a8ec0 (commit)
from c868ef8d18322adf14ee1cd6d004b3a263c55861 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2980df20a6a19cf83dffecffd8bf2b997c086ac1
commit 2980df20a6a19cf83dffecffd8bf2b997c086ac1
Merge: c868ef8 1c2508a
Author: Bj�rn Ricks bjoern.ri...@intevation.de
AuthorDate: Tue Aug 23 03:56:33 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Aug 23 03:56:33 2011 -0400
Merge topic 'FindPythonInterp-Refactoring' into next
1c2508a Use FIND_PACKAGE_HANDLE_STANDARD_ARGS second mode
d179500 Update documentation of FindPythonInterp.cmake
4fd1e28 Determine python version
20980ef Search for the installed python interpreter first
fe46e7e KWSys Nightly Date Stamp
29b285c KWSys Nightly Date Stamp
3848b39 KWSys Nightly Date Stamp
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1c2508a569da51041db7345e0c9eb41aa6aaefd9
commit 1c2508a569da51041db7345e0c9eb41aa6aaefd9
Author: Björn Ricks bjoern.ri...@intevation.de
AuthorDate: Tue Aug 23 09:36:17 2011 +0200
Commit: Björn Ricks bjoern.ri...@intevation.de
CommitDate: Tue Aug 23 09:52:35 2011 +0200
Use FIND_PACKAGE_HANDLE_STANDARD_ARGS second mode
Using the second mode of FIND_PACKAGE_HANDLE_STANDARD_ARGS allows for
checking the version number. Now a user can require a minimum version of
the python interpreter with find_package(PythonInterp VERSION)
diff --git a/Modules/FindPythonInterp.cmake b/Modules/FindPythonInterp.cmake
index 7acf7be..a10ec23 100644
--- a/Modules/FindPythonInterp.cmake
+++ b/Modules/FindPythonInterp.cmake
@@ -61,6 +61,6 @@ endif()
# handle the QUIETLY and REQUIRED arguments and set PYTHONINTERP_FOUND to TRUE
if
# all listed variables are TRUE
include(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake)
-FIND_PACKAGE_HANDLE_STANDARD_ARGS(PythonInterp DEFAULT_MSG PYTHON_EXECUTABLE)
+FIND_PACKAGE_HANDLE_STANDARD_ARGS(PythonInterp REQUIRED_VARS PYTHON_EXECUTABLE
VERSION_VAR PYTHON_VERSION_STRING)
mark_as_advanced(PYTHON_EXECUTABLE)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d1795002956f8da746077fffb1c2aa0262063db2
commit d1795002956f8da746077fffb1c2aa0262063db2
Author: Björn Ricks bjoern.ri...@intevation.de
AuthorDate: Fri Aug 5 09:53:39 2011 +0200
Commit: Björn Ricks bjoern.ri...@intevation.de
CommitDate: Tue Aug 23 09:52:28 2011 +0200
Update documentation of FindPythonInterp.cmake
Document new variables and update also comments in cmake code to explain
the current behaviour of FindPythonInterp.cmake module
diff --git a/Modules/FindPythonInterp.cmake b/Modules/FindPythonInterp.cmake
index 934602d..7acf7be 100644
--- a/Modules/FindPythonInterp.cmake
+++ b/Modules/FindPythonInterp.cmake
@@ -4,11 +4,17 @@
#
# PYTHONINTERP_FOUND - Was the Python executable found
# PYTHON_EXECUTABLE - path to the Python interpreter
-# Python_ADDITIONAL_VERSIONS - list of additional Python versions to search
for
#
+# PYTHON_VERSION_STRING - Python version found e.g. 2.5.2
+# PYTHON_VERSION_MAJOR - Python major version found e.g. 2
+# PYTHON_VERSION_MINOR - Python minor version found e.g. 5
+# PYTHON_VERSION_PATCH - Python patch version found e.g. 2
+#
+# Python_ADDITIONAL_VERSIONS - list of additional Python versions to search
for
#=
# Copyright 2005-2010 Kitware, Inc.
+# Copyright 2011 Bjoern Ricks bjoern.ri...@gmail.com
#
# Distributed under the OSI-approved BSD License (the License);
# see accompanying file Copyright.txt for details.
@@ -20,6 +26,7 @@
# (To distribute this file outside of CMake, substitute the full
# License text for the above reference.)
+# Search for the current active python version first
find_program(PYTHON_EXECUTABLE NAMES python)
# Set up the versions we know about, in the order we will search. Always add
@@ -28,8 +35,7 @@ set(_Python_VERSIONS
${Python_ADDITIONAL_VERSIONS}
2.7 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.6 1.5)
-# Run first with
[Cmake-commits] CMake branch, next, updated. v2.8.5-1690-g83dc7d0
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 83dc7d053e72d22c398f18b6038dcd3a3404b2ec (commit)
via 03d60c7d818584c5c44d2992b6cba1e202cdd498 (commit)
via 6adeda9f55ca81b3715dd7512f2cd3c3218bd6ab (commit)
via e253348ecd8cedc0f5fe640e613b2d19bd5641ae (commit)
via 32eff0caec8fa896fdbb58d259c5cff2614279c3 (commit)
from 6fb8c88e9b102ab21f8467b1dbec39afb047ad7f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=83dc7d053e72d22c398f18b6038dcd3a3404b2ec
commit 83dc7d053e72d22c398f18b6038dcd3a3404b2ec
Merge: 6fb8c88 03d60c7
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Aug 23 14:11:44 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Aug 23 14:11:44 2011 -0400
Merge topic 'generate_export_header' into next
03d60c7 Try to make the macros do almost nothing for Watcom.
6adeda9 Possibly fix configuration test on AIX.
e253348 Possibly fix test on HPUX.
32eff0c Test for too-old-intel compilers.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=03d60c7d818584c5c44d2992b6cba1e202cdd498
commit 03d60c7d818584c5c44d2992b6cba1e202cdd498
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Aug 23 20:04:56 2011 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Tue Aug 23 20:07:42 2011 +0200
Try to make the macros do almost nothing for Watcom.
diff --git a/Modules/GenerateExportHeader.cmake
b/Modules/GenerateExportHeader.cmake
index 1d4c482..6225f70 100644
--- a/Modules/GenerateExportHeader.cmake
+++ b/Modules/GenerateExportHeader.cmake
@@ -160,7 +160,13 @@ macro(_test_compiler_hidden_visibility)
# Exclude XL here because it misinterprets -fvisibility=hidden even though
# the check_cxx_compiler_flag passes
# http://www.cdash.org/CDash/testDetails.php?test=109109951build=1419259
- if (NOT GCC_TOO_OLD AND NOT _INTEL_TOO_OLD AND NOT WIN32 AND NOT CYGWIN AND
NOT ${CMAKE_CXX_COMPILER_ID} MATCHES XL AND NOT ${CMAKE_CXX_COMPILER_ID}
MATCHES PGI)
+ if (NOT GCC_TOO_OLD
+ AND NOT _INTEL_TOO_OLD
+ AND NOT WIN32
+ AND NOT CYGWIN
+ AND NOT ${CMAKE_CXX_COMPILER_ID} MATCHES XL
+ AND NOT ${CMAKE_CXX_COMPILER_ID} MATCHES PGI
+ AND NOT ${CMAKE_CXX_COMPILER_ID} MATCHES Watcom)
check_cxx_compiler_flag(-fvisibility=hidden COMPILER_HAS_HIDDEN_VISIBILITY)
check_cxx_compiler_flag(-fvisibility-inlines-hidden
COMPILER_HAS_HIDDEN_INLINE_VISIBILITY)
option(USE_COMPILER_HIDDEN_VISIBILITY Use HIDDEN visibility support if
available. ON)
@@ -169,7 +175,11 @@ macro(_test_compiler_hidden_visibility)
endmacro()
macro(_test_compiler_has_deprecated)
- if(${CMAKE_CXX_COMPILER_ID} MATCHES Borland OR ${CMAKE_CXX_COMPILER_ID}
MATCHES HP OR GCC_TOO_OLD OR ${CMAKE_CXX_COMPILER_ID} MATCHES PGI)
+ if(${CMAKE_CXX_COMPILER_ID} MATCHES Borland
+ OR ${CMAKE_CXX_COMPILER_ID} MATCHES HP
+ OR GCC_TOO_OLD
+ OR ${CMAKE_CXX_COMPILER_ID} MATCHES PGI
+ OR ${CMAKE_CXX_COMPILER_ID} MATCHES Watcom)
set(COMPILER_HAS_DEPRECATED CACHE INTERNAL Compiler support for a
deprecated attribute)
else()
_check_cxx_compiler_attribute(__attribute__((__deprecated__))
COMPILER_HAS_DEPRECATED_ATTR)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6adeda9f55ca81b3715dd7512f2cd3c3218bd6ab
commit 6adeda9f55ca81b3715dd7512f2cd3c3218bd6ab
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Aug 23 19:58:42 2011 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Tue Aug 23 19:58:42 2011 +0200
Possibly fix configuration test on AIX.
diff --git a/Modules/CheckCXXCompilerFlag.cmake
b/Modules/CheckCXXCompilerFlag.cmake
index 788bf35..91008c3 100644
--- a/Modules/CheckCXXCompilerFlag.cmake
+++ b/Modules/CheckCXXCompilerFlag.cmake
@@ -33,6 +33,7 @@ MACRO (CHECK_CXX_COMPILER_FLAG _FLAG _RESULT)
FAIL_REGEX [Uu]nknown option # HP
FAIL_REGEX [Ww]arning: [Oo]ption # SunPro
FAIL_REGEX command option .* is not recognized # XL
+ FAIL_REGEX not supported in this configuration; ignored # AIX
)
SET (CMAKE_REQUIRED_DEFINITIONS ${SAFE_CMAKE_REQUIRED_DEFINITIONS})
ENDMACRO (CHECK_CXX_COMPILER_FLAG)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e253348ecd8cedc0f5fe640e613b2d19bd5641ae
commit e253348ecd8cedc0f5fe640e613b2d19bd5641ae
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Aug 23 19:49:52 2011 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Tue Aug 23 19:49:52 2011 +0200
Possibly fix test on HPUX.
diff --git
[Cmake-commits] CMake branch, master, updated. v2.8.5-204-gee45a5d
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via ee45a5dd5a1c10e98de4623ba0c17f79ccfcd3d8 (commit) from fe46e7e4866bd1a7678e1381da02df8c9f533aa0 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ee45a5dd5a1c10e98de4623ba0c17f79ccfcd3d8 commit ee45a5dd5a1c10e98de4623ba0c17f79ccfcd3d8 Author: KWSys Robot kwro...@kitware.com AuthorDate: Wed Aug 24 00:01:04 2011 -0400 Commit: KWSys Robot kwro...@kitware.com CommitDate: Wed Aug 24 00:14:07 2011 -0400 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 15abe5a..fa2cab5 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2011) SET(KWSYS_DATE_STAMP_MONTH 08) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 23) +SET(KWSYS_DATE_STAMP_DAY 24) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
