[CMake] INTERNAL vs. STATIC cache variables
Hi all, Is there a difference in precedence between INTERNAL and STATIC cache variables? For example, what happens if I (accidentally) define an INTERNAL cache variable that is already or will be defined by CMake? Will the STATIC variable always have precedence? Or am I entering the realm of undefined behavior? Best regards, Marcel Loose. ___ 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] Link against dynamic library
Hello, Is there any way to tell cmake to use relative paths when linking an executable? Here some info about a sample exec: $ otool -L ./rtmpserver/rtmpserver ./rtmpserver/rtmpserver: /Users/shiretu/work/crtmpserver/trunk/builders/cmake/thelib/ libthelib.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /Users/shiretu/work/crtmpserver/trunk/builders/cmake/common/ libcommon.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 124.1.1) What I want is to transform /Users/shiretu/work/crtmpserver/trunk/builders/cmake/thelib/ libthelib.dylib (compatibility version 0.0.0, current version 0.0.0) into thelib/libthelib.dylib (compatibility version 0.0.0, current version 0.0.0) So, when I do TARGET_LINK_LIBRARIES(rtmpserver thelib.) is there any way to tell cmake to build the Makefile in such a way that the final executable will have relative references to the used libraries? I only want to do that for the libraries in my project, not all of them (ibSystem.B.dylib,libstdc++.6.dylib, etc) should remain the same Thank you ___ 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] Link against dynamic library
With CMake you can do something like:
add_library(foo )
add_executable( bar .. )
target_link_libraries (bar foo)
and CMake will make sure all the link paths are correct. There
generally should not be a need to set the install_name of built
libraries _within_ a build tree.
Now, setting the install_name for an installation is a different
matter. If you are creating OS X .app bundles then you should look
into CMake's BundleUtilities module that fixes up OS X .app
bundles for self contained deployment.
If you are building libraries that you are installing onto your system
to mimic an actual installation on another machine then I have the
following bit of code in my CMakeLists.txt file for each library
project:
IF (APPLE)
OPTION (MXA_BUILD_WITH_INSTALL_NAME Build Libraries with the
install_name set to the installation prefix. This is good if you are
going to run from the installation location OFF)
IF(MXA_BUILD_WITH_INSTALL_NAME)
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME}
PROPERTIES
LINK_FLAGS -current_version ${${PROJECT_NAME}_VERSION} -
compatibility_version ${${PROJECT_NAME}_VERSION}
INSTALL_NAME_DIR ${CMAKE_INSTALL_PREFIX}/lib
BUILD_WITH_INSTALL_RPATH ${MXA_BUILD_WITH_INSTALL_NAME}
)
ENDIF(MXA_BUILD_WITH_INSTALL_NAME)
ENDIF (APPLE)
So when I want to do an actual install of the project somewhere else
on my system I launch ccmake or cmake-gui.app and set the
MXA_BUILD_WITH_INSTALL_NAME option to ON then do a make install and
the makefiles that cmake generates will have the correct OS X
'install_name' set for the particular CMAKE_INSTALL_PREFIX that was
set during configuration.
Does any of that make sense?
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Sep 25, 2009, at 7:28 AM, Eugen-Andrei Gavriloaie wrote:
Hello,
Is there any way to tell cmake to use relative paths when linking an
executable? Here some info about a sample exec:
$ otool -L ./rtmpserver/rtmpserver
./rtmpserver/rtmpserver:
/Users/shiretu/work/crtmpserver/trunk/builders/cmake/thelib/
libthelib.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current
version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8,
current version 0.9.8)
/Users/shiretu/work/crtmpserver/trunk/builders/cmake/common/
libcommon.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.9.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 124.1.1)
What I want is to transform
/Users/shiretu/work/crtmpserver/trunk/builders/cmake/thelib/
libthelib.dylib (compatibility version 0.0.0, current version 0.0.0)
into
thelib/libthelib.dylib (compatibility version 0.0.0, current version
0.0.0)
So, when I do
TARGET_LINK_LIBRARIES(rtmpserver thelib.) is there any way to
tell cmake to build the Makefile in such a way that the final
executable will have relative references to the used libraries?
I only want to do that for the libraries in my project, not all of
them (ibSystem.B.dylib,libstdc++.6.dylib, etc) should remain the same
Thank you
___
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
___
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] Resolution of dependencies for Subversion
Again, to me it looks like FindSubversion is for *using* Subversion, not for building it. As such, setting up include paths and link libraries is not appropriate in that module. Does a naming convention exist for configuration scripts? How should names be distinguished between scripts which look only for the availability of specific client software like the command svn and files which determine all parameters for the build process to enable customised software development? Regards, Markus ___ 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] file1 newer than file2 test
Is there a way to test if one file is newer than another file? Something along the lines if cmake -E compare_files, but for time stamps? I need to copy dlls into the binary directory, but I want to do it conservatively. Also I need different versions for Debug and Release, so add_custom_command doesn't work due to the lack of configuration specific dependencies. Ultimately, what I think I'll have to do is generate a script that takes the build configuration as a parameter and runs copy_if_different as a post build command for a given target. James ___ 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] file1 newer than file2 test
See also the IS_NEWER_THAN clause of the IF command. http://www.cmake.org/cmake/help/cmake2.6docs.html#command:if On Fri, Sep 25, 2009 at 1:47 PM, James Bigler jamesbig...@gmail.com wrote: Is there a way to test if one file is newer than another file? Something along the lines if cmake -E compare_files, but for time stamps? I need to copy dlls into the binary directory, but I want to do it conservatively. Also I need different versions for Debug and Release, so add_custom_command doesn't work due to the lack of configuration specific dependencies. Ultimately, what I think I'll have to do is generate a script that takes the build configuration as a parameter and runs copy_if_different as a post build command for a given target. James ___ 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 ___ 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] Testing for SSE and adding appropriate Compile options
I am testing for SSE2/SSE3 functionality and am having some issues
getting things correct.
After I properly detect that SSE2/3 is available I need to set the
COmpiler Flags. For GCC it seems I should use -msse2 or -msse3
flags. For MSVC it seems I should use /arch:SSE2. So I am trying to
append to CMAKE_C_FLAGS and CMAKE_CXX_FLAGS
by doing the following:
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} -msse3)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -msse3)
for NON MSVC compilers and
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} /arch:SSE2)
for MSVC compilers. The problem seems to be that, at least on windows
that an extra ; is also added, which makes sense as that is how
CMake handles the concatenation of lists. So how best to append to the
CMAKE_C_FLAGS?
Or should I be using the set_source_files_properties() for each file
that needs to have SSE compile flags/options turned on?
Thanks
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
___
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 -E copy_directory' fails
Hi, I am having intermittent trouble executing $ cmake -E copy_directory /full/path/to/large/directory /new/path Originally, the copy_directory was failing deep in my build system (add_custom_command), but the failure is repeatable from the command line (exactly as shown above). The failure message is always the same: $ Error copying directory from /full/path/to/large/directory to /new/path. Does anyone have any thoughts on how to determine the actual cause of the failure. I can execute 'cp -r' reliably without error. I am not sure if this is a failure in CMake or a system problem. The directory in question has about 7000 files in it with a total size of about 75 MB. The copy is going over an NFS mapped drive. I'm using RHEL4 (Nahant Update 8) 64-bit and cmake version 2.6-patch 4. Thanks for any advice! -kt ___ 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] file1 newer than file2 test
Sweet. Thanks! Missed that one after all these years. James On Fri, Sep 25, 2009 at 11:53 AM, David Cole david.c...@kitware.com wrote: See also the IS_NEWER_THAN clause of the IF command. http://www.cmake.org/cmake/help/cmake2.6docs.html#command:if On Fri, Sep 25, 2009 at 1:47 PM, James Bigler jamesbig...@gmail.comwrote: Is there a way to test if one file is newer than another file? Something along the lines if cmake -E compare_files, but for time stamps? I need to copy dlls into the binary directory, but I want to do it conservatively. Also I need different versions for Debug and Release, so add_custom_command doesn't work due to the lack of configuration specific dependencies. Ultimately, what I think I'll have to do is generate a script that takes the build configuration as a parameter and runs copy_if_different as a post build command for a given target. James ___ 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 ___ 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] INTERNAL vs. STATIC cache variables
On Friday 25 September 2009, Marcel Loose wrote: Hi all, Is there a difference in precedence between INTERNAL and STATIC cache variables? For example, what happens if I (accidentally) define an INTERNAL cache variable that is already or will be defined by CMake? Will the STATIC variable always have precedence? Or am I entering the realm of undefined behavior? I think this matters only for the GUI, i.e. ccmake and cmake-gui. INTERNAL variables are hidden there. 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] CMake 2.8.0 RC 1 ready for testing!
I am happy to announce that CMake 2.8.0 has entered the beta stage! You can find the source and binaries here: http://www.cmake.org/files/v2.8/. I am sure I am leaving something out, but here is the list of changes that I came up with. (If you notice something missing please let me know and I will add it to the official release when 2.8.0 is finalized.) Changes in CMake 2.8.0 RC 1 - Qt based GUI cmake-gui is now the default GUI, MFC CMakeSetup is no longer included in CMake. ccmake is still supported. - cmake-gui supports multi-state values options. - CMake now has cmake --build command that can build any CMake generated project from the command line. - Visual Studio 2010 beta support has been added. - Significant improvements for the Eclipse project generator (all targets are now available in Eclipse, system include dirs and predefined macros are now detected so syntax highlighting works better) - KDevelop generator now has color output for builds, and non verbose makefiles. - CTest supports running tests in parallel with a -j N option. - A new CTest CTEST_USE_LAUNCHERS option can be used to get better dashboard error reports with make based tools. - CTest has support for sub-projects and labels which can interact with CDash. - CTest now supports Git, Mercurial, and Bazaar. - It is now possible to use DESTDIR in CPack for any CMake based projects giving more flexibility on the final path names. - The CPack Deb generator now computes the arch instead of hard coding it. - Fortran/C mixed language projects made much easier. CMake now automatically can compute the run time libraries for a compiler. In addition, a new FortranCInterface module can determine the correct name mangling needed to mix C and Fortran. - Intel compiler support added to OSX, and support for embedded manifests in the windows intel compiler was added. - Depend scanning is now much faster with makefiles. - Many FindQt4 improvements to stay working with current Qt releases - FindMPI has improvements for windows. - FindRuby.cmake now supports Ruby 1.9 - FindBoost has been updated to work with the most recent boost releases. - New External Project Module. The 'ExternalProject_Add' function creates a custom target to drive download, update/patch, configure, build, install and test steps of an external project. - xmlrpc dependancy has been removed - CMAKE_OSX_DEPLOYMENT_TARGET cache variable has been created to set the deployment OS for a build on OSX. - Several new policies were added: CMP0012 The if() command can recognize named boolean constants. CMP0013 Duplicate binary directories are not allowed. CMP0014 Input directories must have CMakeLists.txt. CMP0015 The set() CACHE mode and option() command make the cache value visible. - Lots of bug fixes. Please try this version of CMake on your projects and report any issues to the list or the bug tracker ( I have added a CMake-2-8 version ). Happy, building! -Bill ___ 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] Testing for SSE and adding appropriate Compile options
On Fri, Sep 25, 2009 at 01:57:26PM -0400, Michael Jackson wrote:
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} -msse3)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -msse3)
for NON MSVC compilers and
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} /arch:SSE2)
for MSVC compilers. The problem seems to be that, at least on windows
that an extra ; is also added, which makes sense as that is how
CMake handles the concatenation of lists. So how best to append to the
CMAKE_C_FLAGS?
Does it work if you just drop the quotes from the second half of the
set()?
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
or, slightly more pedantically:
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
?
tyler
___
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: add icon to start menu
I'm using the NSIS generator to create a package. Is there a CPACK variable that can be set to add a particular executable to the start menu? I noticed that the start menu is populated with uninstall only. -- Shane ___ 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: add icon to start menu
On Fri, Sep 25, 2009 at 4:36 PM, Dixon, Shane shane.di...@atmel.com wrote:
I’m using the NSIS generator to create a package. Is there a CPACK variable
that can be set to add a particular executable to the start menu? I noticed
that the start menu is populated with “uninstall” only.
This works for me. Here is that part of my CMakeLists.txt
IF(PACKAGE_FOR_INSTALL)
SET(CPACK_PACKAGE_VERSION_MAJOR ${LungAnalysis_VERSION_MAJOR})
SET(CPACK_PACKAGE_VERSION_MINOR ${LungAnalysis_VERSION_MINOR})
SET(CPACK_PACKAGE_VERSION_PATCH ${LungAnalysis_VERSION_PATCH})
IF(CMAKE_CL_64)
SET(CMAKE_MSVC_ARCH amd64)
ELSE(CMAKE_CL_64)
SET(CMAKE_MSVC_ARCH x86)
ENDIF(CMAKE_CL_64)
IF(MSVC80)
FIND_PROGRAM(MSVC_REDIST NAMES
vcredist_${CMAKE_MSVC_ARCH}/vcredist_${CMAKE_MSVC_ARCH}.exe
PATHS
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\8.0;InstallDir]/../../SDK/v2.0/BootStrapper/Packages/
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\8.0;InstallDir]/../../SDK/v2.0/BootStrapper/Packages/
)
GET_FILENAME_COMPONENT(vcredist_name ${MSVC_REDIST} NAME)
INSTALL(PROGRAMS ${MSVC_REDIST} COMPONENT Runtime DESTINATION bin)
SET(CPACK_NSIS_EXTRA_INSTALL_COMMANDS ExecWait
'\\\$INSTDIRbin${vcredist_name}\\\')
ENDIF(MSVC80)
IF(UNIX AND NOT APPLE)
INSTALL(TARGETS HyvesDesktop
DESTINATION bin
)
FOREACH(LIB QtCore QtXml QtTest QtGui QtNetwork QtScript)
INSTALL(FILES
${QT_LIBRARY_DIR}/lib${LIB}.so.${QT_VERSION_MAJOR}.${QT_VERSION_MINOR}.${QT_VERSION_PATCH}
RENAME lib${LIB}.so.${QT_VERSION_MAJOR}
DESTINATION bin
)
ENDFOREACH(LIB)
ENDIF(UNIX AND NOT APPLE)
IF(WIN32)
SET(CPACK_NSIS_COMPRESSOR /SOLID lzma)
SET(CPACK_PACKAGE_EXECUTABLES LungAnalysis Lung Analysis)
INSTALL(FILES
${QT_LIBRARY_DIR}/QtCore${QT_VERSION_MAJOR}.dll
${QT_LIBRARY_DIR}/QtXml${QT_VERSION_MAJOR}.dll
${QT_LIBRARY_DIR}/QtTest${QT_VERSION_MAJOR}.dll
${QT_LIBRARY_DIR}/QtGui${QT_VERSION_MAJOR}.dll
${QT_LIBRARY_DIR}/QtNetwork${QT_VERSION_MAJOR}.dll
${QT_LIBRARY_DIR}/QtScript${QT_VERSION_MAJOR}.dll
DESTINATION bin
COMPONENT Applications
)
ENDIF(WIN32)
set(CPACK_COMPONENTS_ALL Applications Runtime)
INCLUDE(CPack)
ENDIF(PACKAGE_FOR_INSTALL)
___
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] Testing for SSE and adding appropriate Compile options
Michael Jackson wrote:
Does it work if you just drop the quotes from the second half of the
set()?
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
or, slightly more pedantically:
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
Nope, this variable is a string and not a list.
It has to be like this:
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} /arch:SSE2)
-Bill
___
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] Testing for SSE and adding appropriate Compile options
I tried that also and it didn't work either. I am not at my windows
box at the moment to get the exact error. I now have
if (AIMBLADE_USE_SSE)
set_source_files_properties(${SymmetryFilter_SOURCE_DIR}/
FFThread.cpp
${SymmetryFilter_SOURCE_DIR}/
FFNormalizeThread.h
${AIMBlades_SOURCE_DIR}/Source/AIM/Common/
AIMArray_SSE.hpp
${SymmetryFilter_SOURCE_DIR}/
LengthScaleData.cpp
PROPERTIES COMPILE_FLAGS $
{SSE_COMPILE_FLAGS} )
endif()
although I was trying all that on a non-clean build folder (.. I
know.. ) so there may have been some slop still left over from other
configuration runs..
Is there a CMake Standard for looking for SSE and what to do? I
tried looking through the ITK sources for inspiration but ITK is
pretty complex to try and grep through the sources.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Sep 25, 2009, at 5:01 PM, Bill Hoffman wrote:
Michael Jackson wrote:
Does it work if you just drop the quotes from the second half of the
set()?
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
or, slightly more pedantically:
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} /arch:SSE2)
Nope, this variable is a string and not a list.
It has to be like this:
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} /arch:SSE2)
-Bill
___
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
___
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 2.8.0 RC 1 ready for testing!
Hello, Wow, this is really a surprise. I was not expecting CMake 2.8.0 until at least mid-2010! What's the expected release date for 2.8.0 final ? On Fri, Sep 25, 2009 at 10:07 PM, Bill Hoffman bill.hoff...@kitware.com wrote: I am happy to announce that CMake 2.8.0 has entered the beta stage! You can find the source and binaries here: http://www.cmake.org/files/v2.8/. I am sure I am leaving something out, but here is the list of changes that I came up with. (If you notice something missing please let me know and I will add it to the official release when 2.8.0 is finalized.) Changes in CMake 2.8.0 RC 1 - Qt based GUI cmake-gui is now the default GUI, MFC CMakeSetup is no longer included in CMake. ccmake is still supported. - cmake-gui supports multi-state values options. - CMake now has cmake --build command that can build any CMake generated project from the command line. - Visual Studio 2010 beta support has been added. - Significant improvements for the Eclipse project generator (all targets are now available in Eclipse, system include dirs and predefined macros are now detected so syntax highlighting works better) - KDevelop generator now has color output for builds, and non verbose makefiles. - CTest supports running tests in parallel with a -j N option. - A new CTest CTEST_USE_LAUNCHERS option can be used to get better dashboard error reports with make based tools. - CTest has support for sub-projects and labels which can interact with CDash. - CTest now supports Git, Mercurial, and Bazaar. - It is now possible to use DESTDIR in CPack for any CMake based projects giving more flexibility on the final path names. - The CPack Deb generator now computes the arch instead of hard coding it. - Fortran/C mixed language projects made much easier. CMake now automatically can compute the run time libraries for a compiler. In addition, a new FortranCInterface module can determine the correct name mangling needed to mix C and Fortran. - Intel compiler support added to OSX, and support for embedded manifests in the windows intel compiler was added. - Depend scanning is now much faster with makefiles. - Many FindQt4 improvements to stay working with current Qt releases - FindMPI has improvements for windows. - FindRuby.cmake now supports Ruby 1.9 - FindBoost has been updated to work with the most recent boost releases. - New External Project Module. The 'ExternalProject_Add' function creates a custom target to drive download, update/patch, configure, build, install and test steps of an external project. - xmlrpc dependancy has been removed - CMAKE_OSX_DEPLOYMENT_TARGET cache variable has been created to set the deployment OS for a build on OSX. - Several new policies were added: CMP0012 The if() command can recognize named boolean constants. CMP0013 Duplicate binary directories are not allowed. CMP0014 Input directories must have CMakeLists.txt. CMP0015 The set() CACHE mode and option() command make the cache value visible. - Lots of bug fixes. Please try this version of CMake on your projects and report any issues to the list or the bug tracker ( I have added a CMake-2-8 version ). Happy, building! -Bill ___ 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 -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ___ 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 2.8.0 RC 1 ready for testing!
I was too fast I forgot the list 2009/9/25 Bill Hoffman bill.hoff...@kitware.com: I am happy to announce that CMake 2.8.0 has entered the beta stage! You can find the source and binaries here: http://www.cmake.org/files/v2.8/. Just built and tested on somes projects. Awesome, works like a charm. For those of you which wants to give it a try without messing-up there install I offer to share a stupid (but useful to me) update-alternatives script which use update-alternatives(8) to switch / install cmake version installed on your machine. usage is simple: 1) Modify CMAKE_HOME in order make it point to your CMake 2.8 install location $ cmake-alternatives-2.8.sh on will install the alternative. The script is attached to the mail. If some of you find it useful this kind of script can even be put in the CMake source tree and CONFIGURE_FILEd + INSTALLed along with cmake in share/cmake-version/scripts. - Lots of bug fixes. Like you said at least 3 for CPack RPM, I did update the CPack pending bugs or features lists: http://www.itk.org/Wiki/CMake:CPackPackageGenerators#CPack_RPM_currently_pending_bugs.2Ffeatures rpm 4.6.x users should definitely try CMake 2.8. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org cmake-alternatives-2.8.sh Description: Bourne shell script ___ 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 2.8.0 RC 1 ready for testing!
Where can I find more info on - Fortran/C mixed language projects made much easier. CMake now automatically can compute the run time libraries for a compiler. Does that mean there is a variable I can use instead of manually specifying libgfortran, libg2c and others depending on the compiler used? I can't seem to find anything like that in Modules/* Thanks, Clint On Friday 25 September 2009 02:07:21 pm Bill Hoffman wrote: I am happy to announce that CMake 2.8.0 has entered the beta stage! You can find the source and binaries here: http://www.cmake.org/files/v2.8/. I am sure I am leaving something out, but here is the list of changes that I came up with. (If you notice something missing please let me know and I will add it to the official release when 2.8.0 is finalized.) Changes in CMake 2.8.0 RC 1 - Qt based GUI cmake-gui is now the default GUI, MFC CMakeSetup is no longer included in CMake. ccmake is still supported. - cmake-gui supports multi-state values options. - CMake now has cmake --build command that can build any CMake generated project from the command line. - Visual Studio 2010 beta support has been added. - Significant improvements for the Eclipse project generator (all targets are now available in Eclipse, system include dirs and predefined macros are now detected so syntax highlighting works better) - KDevelop generator now has color output for builds, and non verbose makefiles. - CTest supports running tests in parallel with a -j N option. - A new CTest CTEST_USE_LAUNCHERS option can be used to get better dashboard error reports with make based tools. - CTest has support for sub-projects and labels which can interact with CDash. - CTest now supports Git, Mercurial, and Bazaar. - It is now possible to use DESTDIR in CPack for any CMake based projects giving more flexibility on the final path names. - The CPack Deb generator now computes the arch instead of hard coding it. - Fortran/C mixed language projects made much easier. CMake now automatically can compute the run time libraries for a compiler. In addition, a new FortranCInterface module can determine the correct name mangling needed to mix C and Fortran. - Intel compiler support added to OSX, and support for embedded manifests in the windows intel compiler was added. - Depend scanning is now much faster with makefiles. - Many FindQt4 improvements to stay working with current Qt releases - FindMPI has improvements for windows. - FindRuby.cmake now supports Ruby 1.9 - FindBoost has been updated to work with the most recent boost releases. - New External Project Module. The 'ExternalProject_Add' function creates a custom target to drive download, update/patch, configure, build, install and test steps of an external project. - xmlrpc dependancy has been removed - CMAKE_OSX_DEPLOYMENT_TARGET cache variable has been created to set the deployment OS for a build on OSX. - Several new policies were added: CMP0012 The if() command can recognize named boolean constants. CMP0013 Duplicate binary directories are not allowed. CMP0014 Input directories must have CMakeLists.txt. CMP0015 The set() CACHE mode and option() command make the cache value visible. - Lots of bug fixes. Please try this version of CMake on your projects and report any issues to the list or the bug tracker ( I have added a CMake-2-8 version ). Happy, building! -Bill ___ 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 ___ 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 -E copy_directory' fails
On Fri, Sep 25, 2009 at 12:06 PM, Eric Noulard eric.noul...@gmail.comwrote: 2009/9/25 Kelly (KT) Thompson k...@transpireinc.com: Hi, I am having intermittent trouble executing $ cmake -E copy_directory /full/path/to/large/directory /new/path Originally, the copy_directory was failing deep in my build system (add_custom_command), but the failure is repeatable from the command line (exactly as shown above). The failure message is always the same: $ Error copying directory from /full/path/to/large/directory to /new/path. Does anyone have any thoughts on how to determine the actual cause of the failure. May be you can try to strace the execution in order to see where it fails? Great idea. (Now why didn't I think of that?!?) Strace found the problem. There was an invalid symbolic link buried deep in my directory structure that was failing with ENOENT (No such file or directory). I guess cp blindly copies the symlink w/o checking for the existence of the target. Thanks! ___ 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 2.8.0 RC 1 ready for testing!
On Fri, Sep 25, 2009 at 5:31 PM, Pau Garcia i Quiles pgqui...@elpauer.org wrote: Hello, Wow, this is really a surprise. I was not expecting CMake 2.8.0 until at least mid-2010! What's the expected release date for 2.8.0 final ? As soon as the major issues with 2.8.0 rc's are worked out. Nothing really show stopping has showed up yet... :) -Bill ___ 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
