[cmake-developers] Mixing generator expressions and debug|optimized|general keywords in target_link_libraries()
I tried wrapping the libraries returned by FindBoost.cmake in $BUILD_INTERFACE in a target_link_libraries() call and noticed that this breaks because of the debug/optimized keywords that the find module inserts. Specifically it results in CMake trying to link e.g. optimized.lib. Should/could these keywords be handled at generation time (after generator expressions expansion)? There don't seem to be generator expressions that correspond to the debug/optimized keywords exactly. Can/should there be? e.g. $DEBUG: and $OPTIMIZED: output expressions. The former expanding when the current configuration is listed in the directory property DEBUG_CONFIGURATIONS. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] Cross compile tests on open.cdash.org
Hi Everybody I'm interested in cross compilation, and am already using it extensively for Linux and Embedded Linux. But now I ran into some problems cross compiling for Windows Compact Embedded 2013 using Visual Studio. After some discussion on IRC, Nils Gladitz pointed out that there are no cross compilation tests on the public CDash (http://open.cdash.org/index.php?project=CMake). It might be worth to start a discussion on that topic and maybe find a way to improve that. One question is if there is already somebody working in this direction or maybe even already has a running cross compilation test using CMake? What would be necessary to extend the current test for a cross compilation scenario? With best regards, Pascal Bach Siemens Building Technologies Division HQ (dARE of 5280) Infrastructure Cities Sector Building Technologies Control Products Systems IC BT CPS RD ZG FW CCP Gubelstrasse 22 6300 Zug, Switzerland Tel: +41 41 724-2535 mailto:pascal.b...@siemens.com www.siemens.ch -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Cross compile tests on open.cdash.org
On 8/29/2014 9:47 AM, Bach, Pascal wrote: Hi Everybody I'm interested in cross compilation, and am already using it extensively for Linux and Embedded Linux. But now I ran into some problems cross compiling for Windows Compact Embedded 2013 using Visual Studio. After some discussion on IRC, Nils Gladitz pointed out that there are no cross compilation tests on the public CDash (http://open.cdash.org/index.php?project=CMake). It might be worth to start a discussion on that topic and maybe find a way to improve that. One question is if there is already somebody working in this direction or maybe even already has a running cross compilation test using CMake? What would be necessary to extend the current test for a cross compilation scenario? With best regards, Pascal Bach Hi, This is a good idea. There has been some recent work on the windows phone support: Tests/VSWinStorePhone/. However, I would think what you would want would be a more comprehensive test of CMake. Most of the tests run executables that are built. We would either have to not do that, or run them on a simulator or have an actual device that the tests are pushed to for running. The other option would be to create one or more specific cross compile tests. It would require someone to setup dashboard clients as well: http://www.cmake.org/cmake/resources/testing.html. Would you be able to run clients like that? -Bill -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015116]: cmake add_custom_command issue with multiple output files
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15116 == Reported By:Vijay Pradeep Assigned To: == Project:CMake Issue ID: 15116 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2014-08-29 13:11 EDT Last Modified: 2014-08-29 13:11 EDT == Summary:cmake add_custom_command issue with multiple output files Description: I'm noticing some potential incorrect behavior in cmake when working with add_custom_command and multiple output files. I've been able to isolate the problem to a minimal example (see below). It seems that when I have two output files specified in my add_custom_command, the second output file's upstream dependencies are not being tracked correctly in some cases. The cmake documentation clearly mentions that multiple output files are allowed. What's interesting here is that swapping the order of the output files causes different behavior, suggesting that the first OUTPUT file is being treated differently. (Crossposted here: http://stackoverflow.com/questions/24416133/cmake-add-custom-command-issue-with-multiple-output-files) Steps to Reproduce: Example CMakeLists.txt: cmake_minimum_required(VERSION 2.8) add_library(mybaz baz.cpp) add_custom_command( OUTPUT baz2.cpp COMMAND cp baz.cpp baz2.cpp DEPENDS baz.cpp COMMENT Copying baz.cpp to baz2.cpp) add_custom_target(mytarget DEPENDS baz2.cpp COMMENT Running mytarget) add_dependencies(mybaz mytarget) add_custom_command( OUTPUT bar.cpp baz.cpp COMMAND cat a.txt bar.cpp COMMAND cat a.txt baz.cpp DEPENDS a.txt COMMENT Generating bar.cpp and baz.cpp) == Below are the commands that I run: touch a.txt cmake . ...snip... (configuration runs fine) make Scanning dependencies of target mytarget [ 20%] Generating bar.cpp and baz.cpp [ 40%] Copying baz.cpp to baz2.cpp [ 60%] Running mytarget [ 60%] Built target mytarget Scanning dependencies of target mybaz [ 80%] Building CXX object CMakeFiles/mybaz.dir/baz.cpp.o Linking CXX static library libmybaz.a [100%] Built target mybaz (everything looks good) touch a.txt make [ 20%] Generating bar.cpp and baz.cpp [ 40%] Running mytarget [ 60%] Built target mytarget Scanning dependencies of target mybaz [ 80%] Building CXX object CMakeFiles/mybaz.dir/baz.cpp.o Linking CXX static library libmybaz.a [100%] Built target mybaz (I seem to be missing the 'Copying baz.cpp to baz2.cpp' line) make [ 20%] Copying baz.cpp to baz2.cpp [ 40%] Running mytarget [ 60%] Built target mytarget [100%] Built target mybaz ( The 'Copying baz.cpp to baz2.cpp' executes this time ) == Issue History Date ModifiedUsername FieldChange == 2014-08-29 13:11 Vijay Pradeep New Issue == -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015117]: InstallRequiredSystemLibraries does not install OpenMP library on MSVC
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15117
==
Reported By:Greg Sharp
Assigned To:
==
Project:CMake
Issue ID: 15117
Category: (No Category)
Reproducibility:have not tried
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2014-08-29 16:40 EDT
Last Modified: 2014-08-29 16:40 EDT
==
Summary:InstallRequiredSystemLibraries does not install
OpenMP library on MSVC
Description:
Programs compiled with MSVC which use OpenMP require the vcomp${ver}.dll runtime
library. The Module InstallRequiredSystemLibraries.cmake is normally
responsible for adding needed libraries (such as C runtime library) to install
targets. However, it misses the OpenMP libraries.
Additional Information:
A web search reveals many reports of this issue, and various workarounds. For
example:
http://www.cmake.org/pipermail/cmake/2012-September/051964.html
http://gmt.soest.hawaii.edu/issues/27
http://braintrekking.wordpress.com/2013/04/27/dll-hell-how-to-include-microsoft-redistributable-runtime-libraries-in-your-cmakecpack-project/
==
Issue History
Date ModifiedUsername FieldChange
==
2014-08-29 16:40 Greg Sharp New Issue
==
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015118]: ExternalProject_Add SOURCE_DIR field overrides DOWNLOAD_DIR field
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15118
==
Reported By:Umar Arshad
Assigned To:
==
Project:CMake
Issue ID: 15118
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2014-08-30 00:49 EDT
Last Modified: 2014-08-30 00:49 EDT
==
Summary:ExternalProject_Add SOURCE_DIR field overrides
DOWNLOAD_DIR field
Description:
Setting the SOURCE_DIR field forces the download of a repository to that
directory instead of the DOWNLOAD_DIR directory. This seems counter to what the
documentation suggest since the SOURCE_DIR field is under the configuration
section. This makes it difficult to add projects who's CMakeLists.txt files are
not in the root folder of the repository (i.e. clBLAS)
DOWNLOAD_DIR should be where the project is downloaded/cloned
SOURCE_DIR should be the location of the CMakeLists.txt file
Steps to Reproduce:
# Set default ExternalProject root directory
set_directory_properties(PROPERTIES EP_PREFIX ${CMAKE_BINARY_DIR}/third_party)
ExternalProject_Add(
clBlas
GIT_REPOSITORY ssh://g...@github.com/clMathLibraries/clBLAS.git
GIT_TAG v2.2
TIMEOUT 10
DOWNLOAD_DIR ${CMAKE_BINARY_DIR}/third_party/src/clBlas
SOURCE_DIR ${CMAKE_BINARY_DIR}/third_party/src/clBlas/src
CMAKE_ARGS -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}
-DCMAKE_ARCHIVE_OUTPUT_DIRECTORY_DEBUG:PATH=DebugLibs
-DCMAKE_ARCHIVE_OUTPUT_DIRECTORY_RELEASE:PATH=ReleaseLibs
-DCMAKE_CXX_COMPILER=${CMAKE_CXX_COMPILER}
-DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS})
==
Issue History
Date ModifiedUsername FieldChange
==
2014-08-30 00:49 Umar ArshadNew Issue
2014-08-30 00:49 Umar ArshadFile Added: BuildCLBLAS.cmake
==
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
