[CMake] How can I silence a cmake warning?

Hi All Quick question: how can silence the following warnings? Thank you! CMake Warning at cmake/TargetFunctions.cmake:383 (add_library): Cannot generate a safe runtime search path for target pyfinlinearPy because there is a cycle in the constraint graph: dir 0 is [/some/path] dir 2 must prece

Re: [CMake] CPack with BZIP2 is a lot slower than GNU tar

atements in our CMakeLists.txt files. On 2 June 2016 at 06:14, Raymond Wan wrote: > Hi, > > > On Wed, Jun 1, 2016 at 8:26 PM, Alessio > wrote: > > Is anyone else having problems with the speed of cpack? > > > > Out of one of our code bases we produce two packages on Linux u

[CMake] CPack with BZIP2 is a lot slower than GNU tar

Hi All Is anyone else having problems with the speed of cpack? Out of one of our code bases we produce two packages on Linux using the BZIP2 generator with CMake 3.4.0. I provide a few stats on the packages below. They are not particularly fat. GNU tar will take ~1min to tar the biggest one up wi

Re: [CMake] install(TARGETS) does not work with configuration-specific destinations

OMPONENT ${component} CONFIGURATIONS Debug PDebug RUNTIME DESTINATION "${${PROJECT_NAME}_INSTALL_RUNTIME_DEBUG}" LIBRARY DESTINATION "${${PROJECT_NAME}_INSTALL_RUNTIME_DEBUG}") On 8 June 2015 at 18:40, Alessio wrote: > I forgot to ment

Re: [CMake] install(TARGETS) does not work with configuration-specific destinations

RUNTIME_RELEASE}" CONFIGURATIONS Release RelWithDebInfo MinSizeRel) install( FILES "$/some_file.txt" COMPONENT platform DESTINATION "${${PROJECT_NAME}_INSTALL_RUNTIME_DEBUG}" CONFIGURATIONS Debug PDebug) On 8 June 2015 at 18:32, Alessio wrote: > Hi > &

[CMake] install(TARGETS) does not work with configuration-specific destinations

f the configuration. Can this be done at all? Is there a single-call install(TARGETS) signature that gives me what I want? Thank you very much for any light you can shed on this. -alessio THE CMAKE INSTALL CODE WITH THE PROBLEM --- set(${PROJECT

[CMake] EXCLUDE_FROM_DEFAULT_BUILD: a solution that works for both interactive and unattended builds

line builds? Thank you so much for any feedback you can provide on this -alessio -- 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

[CMake] CDash and xUnit test reports

Hi All Quick question: is there a way to add test detail to the CDash dashboard that comes from xunit XML test report files? The tests we configure in ctest are actually fairly fat containers of Boost Test Framework and Python nose tests, so the vanilla ctest report would not provide the team wit

Re: [CMake] Visual Studio add-in: adding non-cmake files as dependencies to trigger re-generation

Works like a charm Thank you very much! On 19 February 2015 at 00:26, Roman Bolshakov wrote: > You might try to use CMAKE_CONFIGURE_DEPENDS ( > http://www.cmake.org/cmake/help/v3.0/prop_dir/CMAKE_CONFIGURE_DEPENDS.html) > property: > > set_property(DIRECTORY APPEND PROPERTY CMAKE_CONFIGURE_DEPE

[CMake] Visual Studio add-in: adding non-cmake files as dependencies to trigger re-generation

Subject: Visual Studio add-in: adding non-cmake files as dependencies to trigger re-generation Hello Is there a way to let the Visual Studio CMake add-in know that it needs to regenerate the project when certain non-cmake files change? I'm reading lists of file names from non-cmake txt files with

[CMake] Problem with Cmake 3.0.2 and MSVC: devenv.com does not print CMAKE_C_COMPILER= during CMakeDetermineCompilerId.cmake

Hi there, For some mysterious reason the invocation in subject does not print out the all-important message CMAKE_C_COMPILER= after the compilation of CompilerIdC.c The invocation in question is in CMakeDetermnineCompilerId.cmake like 188. The CMAKE_C_COMPILER message is the one echo'ed by a the

[CMake] ctest -j and PARALLEL_LEVEL argument

Hi, This one should be a super-quick: does "ctest -j N" also set a default PARALLEL_LEVEL=N for ctest_memcheck and ctest_test? Could not google anything useful out! Thanks in advance! This message has been sent from a Mediobanca S.p.A. email address. The informat

Re: [CMake] Sharing sources between two targets

A static lib does what you want and won't introduce any extra runtime dependecies On 22 Apr 2013 19:45, "Nick Gnedin" wrote: > > Folks, > > I am using CMake to create 2 targets - a stand-alone executable and a > library that can be imported by Python. Both share most of the sources. If > I just s

[CMake] Excluding targets from a solution config in a Visual Studio build

Hi there Is there a way to tell the Visual Studio generators that a target should not be included in “whole solution” builds? With the following sequence A will be excluded from all solution configurations, but B will be included. add_custom_target(A) add_custom_target(B COMMAND echo This is ta

Re: [CMake] Adding convenience links to data files to generated Visual Studio projects

Answering my own question: just add the files to the add_library or add_executable calls. From: Massaro Alessio Sent: 18 April 2012 09:51 To: 'cmake@cmake.org' Subject: Adding convenience links to data files to generated Visual Studio projects Hi there Does anyone know of a

[CMake] Adding convenience links to data files to generated Visual Studio projects

Hi there Does anyone know of a way to add convenience links to data files to generated Visual Studio projects? Basically I'm looking at a way to use VS as a sort of filesystem browser. In Visual Studio one can add "links" to files. They can be double-clicked and opened with a click, but are ot

[CMake] cmake --build switches ANSI color escape codes off in MINGW bash

Hi there Strange thing with ANSI colors Calling cmake --build from a script in a MINGW bash shell will output ANSI colours escape codes as follows ←[0m[ 12%] ←[32mBuilding CXX object basic/CMakeFiles/.. Piping the same script to /bin/less or calling the native make tool directly will rend

[CMake] Passing extra parameters to CTest from a RUN_TESTS visual studio project

Hi there This has been asked before in 2010, but I thought I might check if anything has changed in CMake v2.8.7. Is it possible to specify extra flags for CTest when it's invoked by the post-build script in a Visual Studio RUN_TESTS project? Adding the following to my main CMakeLists.txt, mai

Re: [CMake] find_package(Subversion) fails when run by an automated Jenkins build

services were running under the built-in system account. Thanks very much for the feedback! -Original Message- From: Eric Noulard [mailto:eric.noul...@gmail.com] Sent: 29 February 2012 18:32 To: Massaro Alessio Cc: cmake@cmake.org Subject: Re: [CMake] find_package(Subversion) fails when run by

[CMake] find_package(Subversion) fails when run by an automated Jenkins build

Hi there, Awkward behaviour: My CMakeLists.txt do a find_package(Subversion) Now, I have a Jenkins build server running under domain user XYZ The Jenkins CMake plugin tells me it's trying to do the following: "c:\Program Files\CMake 2.8\bin\cmake.exe" -G "Visual Studio 9 2008"

Re: [CMake] CPack ZIP generator: is there a way to avoid a root directory named ${CPACK_PACKAGE_FILE_NAME} in the zip?

That did it nice and clean. THANK YOU VERY MUCH! -Original Message- From: Eric Noulard [mailto:eric.noul...@gmail.com] Sent: 13 February 2012 23:33 To: Massaro Alessio Cc: cmake@cmake.org Subject: Re: [CMake] CPack ZIP generator: is there a way to avoid a root directory named

[CMake] CPack ZIP generator: is there a way to avoid a root directory named ${CPACK_PACKAGE_FILE_NAME} in the zip?

Hi there The CPack ZIP generator seems to always put all "installed" files in a directory called ${CPACK_PACKAGE_FILE_NAME} So, if ${CPACK_PACKAGE_FILE_NAME}=="xyz", the zip file will have one single "xyz" directory at the root, with all "installed" files placed therein. Does anyone know if the

[CMake] add_test( WORKING_DIRECTORY ) does not actua

Hi there The following message in cmTest.cxx doesn't seem to be accurate for Visual Studio 9. 200   cm->DefineProperty 201 ("WORKING_DIRECTORY", cmProperty::TEST, 202  "The directory from which the test executable will be called.", 203   "If this is not set it is called from the 

Re: [CMake] runtime dependencies for tests

{mod_name} PROPERTIES ENVIRONMENT "PATH=${newPath}") -Original Message- From: Massaro Alessio Sent: 03 February 2012 10:28 To: 'Michael Hertling'; cmake@cmake.org Subject: RE: [CMake] runtime dependencies for tests Thanks to everyone for the feedback! The follow

Re: [CMake] runtime dependencies for tests

cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Michael Hertling Sent: 01 February 2012 02:20 To: cmake@cmake.org Subject: Re: [CMake] runtime dependencies for tests On 01/31/2012 02:43 PM, Massaro Alessio wrote: > Hi There > > I googled near and far, but could not

[CMake] runtime dependencies for tests

Hi There I googled near and far, but could not find a way to tell CTest where to find the 3rd-party DLLs required to run the test executables. In particular my executable targets link with a few Boost DLLs/SOs and obviously require them to run. I understand on the Linux/Solaris I can use RPATH