[cmake-developers] [CMake 0015559]: ctest_test others missing default value documentation for BUILD parameter
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15559
==
Reported By:trsystran
Assigned To:
==
Project:CMake
Issue ID: 15559
Category: Documentation
Reproducibility:N/A
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2015-05-07 05:19 EDT
Last Modified: 2015-05-07 05:19 EDT
==
Summary:ctest_test others missing default value
documentation for BUILD parameter
Description:
At lest ctest_test and ctest_memcheck don't document the default value for the
BUILD parameter, which is ${CTEST_BINARY_DIRECTORY}, like for ctest_build (for
which it's well documented).
==
Issue History
Date ModifiedUsername FieldChange
==
2015-05-07 05:19 trsystran 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
Re: [cmake-developers] [CMake 0011944]: CPackDeb: Support dependencies between components/Debian packages
2015-05-04 9:53 GMT+02:00 Domen Vrankar domen.vran...@gmail.com: Your test managed to find issues with previous code - automatic dependency detection doesn't work on older versions of dpkg-shlibdeps script. I wrote that a bit unclearly... With previous code I meant code that was there already before your patch. Tests now pass on all test platforms. Thanks, Domen -- 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] Patch for write_compiler_detection_header
On 05/07/2015 01:09 AM, Kevin Godby wrote: Apparently on line 250 of WriteCompilerDetectionHeader.cmake, CMake was parsing FILE as a variable instead of a string. Wrapping FILE in quotation marks fixed the problem. Thanks. That fix depends on CMP0054 being set to NEW. This should fix it more generally: WCDH: Fix condition when variables named FILE or PREFIX are defined http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=65e6b115 -Brad -- 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] Missing CPACK_PACKAGE_CONTACT in test for CPackComponentsPrefix
Hi, testing new cmake, I get ctest error for the call # ctest -R CPackComponentsPrefix This is the relevant part in LastTest.log ... CPack: Install projects CPack: - Run preinstall target for: CPackComponentsPrefix CPack: - Install project: CPackComponentsPrefix CPack: Create package CMake Error at /usr/src/cmake/cmake/Modules/CPackDeb.cmake:386 (message): CPackDeb: Debian package requires a maintainer for a package, set CPACK_PACKAGE_CONTACT or CPACK_DEBIAN_PACKAGE_MAINTAINER Call Stack (most recent call first): /usr/src/cmake/cmake/Modules/CPackDeb.cmake:507 (cpack_deb_prepare_package_vars) CPack Error: Error while execution CPackDeb.cmake ... Adding line set(CPACK_PACKAGE_CONTACT someContact) in Tests/CPackComponentsPrefix/CMakeLists.txt cures the testcase for me. Kornel signature.asc Description: This is a digitally signed message part. -- 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] find_package config mode search path rule #5 error prone
On 07-May-15 00:00, Tamás Kenéz wrote: Hi, The search path rule #5 reads: Search project build trees recently configured in a cmake-gui(1). This can be skipped if NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is building multiple dependent projects one after another. (This step is implemented only on Windows.) I think this rule, while having the best intentions, is error prone (speaking from experience). There are great and proper ways to use the products of a project in a dependent project. Opening the project in cmake-gui to expose the byproduct of a config-module configuration+installation process in the binary dir, is not of them. What do you think, would it be wise to disable this rule with a new policy? Would anybody miss it? Tamas Totally agree, since I am a reporter of this bug: http://public.kitware.com/Bug/view.php?id=14781 As far as I know it works only for GUI version and only on Windows. So does anybody really use such workflow regularly? Ruslo -- 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] [CMake 0011944]: CPackDeb: Support dependencies between components/Debian packages
Would you please add set( CPACK_DEBIAN_PACKAGE_DEBUG ON) to the file MyLibCPackConfig-splitted-components-depend2.cmake.in so that we also have the debug logs? I currently don't have access to my computer so I'll send you that in about a week. Sorry I forgot about this... Attached is verbose output and patch that I was using (slightly modified patch that you provided rebased to current master). Regards, Domen UpdateCTestConfiguration from :/home/domen/Dev/build/cmake/DartConfiguration.tcl Parse Config file:/home/domen/Dev/build/cmake/DartConfiguration.tcl Add coverage exclude regular expressions. Add coverage exclude: XCode Add coverage exclude: Kdevelop Add coverage exclude: /Source/(cm|kw)sys/ Add coverage exclude: /CMakeFiles/CMakeTmp/ Add coverage exclude: [A-Za-z]./[Qq]t/qt-.+-opensource-src UpdateCTestConfiguration from :/home/domen/Dev/build/cmake/DartConfiguration.tcl Parse Config file:/home/domen/Dev/build/cmake/DartConfiguration.tcl Test project /home/domen/Dev/build/cmake Constructing a list of tests Guessing configuration NoConfig Done constructing a list of tests Checking test dependency graph... Checking test dependency graph end test 131 Start 131: CPackComponentsDEB-components-depend2 131: Test command: /home/domen/Dev/build/cmake/bin/ctest -C NoConfig --build-and-test /media/sf_Dev/projects/cmake/Tests/CPackComponentsDEB /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2 --build-generator Unix Makefiles --build-project CPackComponentsDEB --build-options -DCMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make -DCPACK_GENERATOR:STRING=DEB -DCPACK_BINARY_DEB:BOOL=ON -DCPackDEBConfiguration=components-depend2 --graphviz=CPackComponentsDEB.dot --test-command /home/domen/Dev/build/cmake/bin/cmake -DCPackComponentsDEB_SOURCE_DIR:PATH=/media/sf_Dev/projects/cmake/Tests/CPackComponentsDEB -DCPackComponentsDEB_BINARY_DIR:PATH=/home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2 -DCPackGen=DEB -DCPackDEBConfiguration=components-depend2 -P /media/sf_Dev/projects/cmake/Tests/CPackComponentsDEB/RunCPackVerifyResult-components-depend2.cmake 131: Test timeout computed to be: 1500 131: Generate graphviz: /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot.mylib... 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot.mylibapp... 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot.mylibapp2... 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot.mylib.dependers... 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot.mylibapp.dependers... 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot.mylibapp2.dependers... 131: Writing /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2/CPackComponentsDEB.dot... 131: Internal cmake changing into directory: /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2 131: CMake output == 131: Configuring 131: Configuring done 131: Generating 131: Generating done 131: Build files have been written to: /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2 131: End CMake output == 131: Change Dir: /home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2 131: 131: Run Clean Command:/usr/bin/make clean 131: 131: Run Build Command:/usr/bin/make 131: [ 16%] Building CXX object CMakeFiles/mylib.dir/mylib.cpp.o 131: [ 33%] Linking CXX static library libmylib.a 131: [ 33%] Built target mylib 131: [ 50%] Building CXX object CMakeFiles/mylibapp.dir/mylibapp.cpp.o 131: [ 66%] Linking CXX executable mylibapp 131: [ 66%] Built target mylibapp 131: [ 83%] Building CXX object CMakeFiles/mylibapp2.dir/mylibapp.cpp.o 131: [100%] Linking CXX executable mylibapp2 131: [100%] Built target mylibapp2 131: Running test command: /home/domen/Dev/build/cmake/bin/cmake -DCPackComponentsDEB_SOURCE_DIR:PATH=/media/sf_Dev/projects/cmake/Tests/CPackComponentsDEB -DCPackComponentsDEB_BINARY_DIR:PATH=/home/domen/Dev/build/cmake/Tests/CPackComponentsDEB/buildDEB-components-depend2 -DCPackGen=DEB -DCPackDEBConfiguration=components-depend2 -P /media/sf_Dev/projects/cmake/Tests/CPackComponentsDEB/RunCPackVerifyResult-components-depend2.cmake 131: Test command failed: /home/domen/Dev/build/cmake/bin/cmake 131: -- = 131: -- CTEST_FULL_OUTPUT (Avoid ctest truncation of output) 131: -- 131: CMAKE_CPACK_COMMAND =
Re: [cmake-developers] [RFC] Remove `-i` from the build command for makefile generators
On 05/06/2015 02:32 PM, Ben Boeckel wrote: I really question the old behavior at all (it's not like it made things magically work), but OK :/ . I'd be OK with replacing it with `-k` without a policy though (it does the same thing but makes the exit code...useful). IIRC when use of -i was introduced we actually used -k first and found it to be inadequate for the needs at the time. Since requirements seem to have changed I think switching to -k is okay. Heh. We were setting MAKECOMMAND, but using ctest_build. Seems the documentation could use some sprucing up :) . See the MakeCommand setting here: http://www.cmake.org/cmake/help/v3.2/manual/ctest.1.html#ctest-build-step It explains both CTEST_BUILD_COMMAND and MAKECOMMAND. What is missing is that ctest_build docs: http://www.cmake.org/cmake/help/v3.2/command/ctest_build.html should reference CTEST_BUILD_COMMAND. Please add that. Thanks, -Brad -- 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] [RFC] Remove `-i` from the build command for makefile generators
On Thu, May 07, 2015 at 13:06:26 -0400, Ben Boeckel wrote: Merged as update-ctest_build-docs. Thanks for the followup commit for clarifying the docs. I hit the problem where CTEST_BUILD_COMMAND makes CTEST_BUILD_FLAGS get ignored. The new wording makes it much clearer :) . --Ben -- 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] [RFC] Remove `-i` from the build command for makefile generators
On Thu, May 07, 2015 at 09:12:43 -0400, Brad King wrote: IIRC when use of -i was introduced we actually used -k first and found it to be inadequate for the needs at the time. Since requirements seem to have changed I think switching to -k is okay. I've merged this into next as replace-make--i. Heh. We were setting MAKECOMMAND, but using ctest_build. Seems the documentation could use some sprucing up :) . See the MakeCommand setting here: http://www.cmake.org/cmake/help/v3.2/manual/ctest.1.html#ctest-build-step It explains both CTEST_BUILD_COMMAND and MAKECOMMAND. What is missing is that ctest_build docs: http://www.cmake.org/cmake/help/v3.2/command/ctest_build.html should reference CTEST_BUILD_COMMAND. Please add that. Merged as update-ctest_build-docs. Thanks, --Ben -- 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
