[cmake-developers] [CMake 0012608]: Unexpected %config file declaration.
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12608 == Reported By:Daniel Morlock Assigned To: == Project:CMake Issue ID: 12608 Category: CPack Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-12-06 05:10 EST Last Modified: 2011-12-06 05:10 EST == Summary:Unexpected %config file declaration. Description: By default, cmake assumes all files in CPACK_ABSOLUTE_DESTINATION_FILES and CPACK_ABSOLUTE_DESTINATION_FILES_COMPONENT to be %config files. Because of this, all files but those in CPACK_RPM_INSTALL_FILES are declared to be %config files in the RPM specs. I'm not sure whether this is an expected behavior - I think all files should be considered to be normal (non-config) files and the user should be able to define (compoment wise) which files should be assumed to be config files. Additional Information: Attached a patch which introduced CPACK_RPM_COMPONENT_CONFIG_FILES which allows the user to define a list of files which should be considered as config files. If this variable is set, all other files are assumes to be non-config files. == Issue History Date ModifiedUsername FieldChange == 2011-12-06 05:10 Daniel Morlock New Issue 2011-12-06 05:10 Daniel Morlock File Added: cmake-2.8.6-CPackRPM.patch == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012609]: Report when CTEST_COVERAGE_COMMAND is not set
The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=12609 == Reported By:Mathieu Malaterre Assigned To: == Project:CMake Issue ID: 12609 Category: CTest Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-12-06 08:11 EST Last Modified: 2011-12-06 08:11 EST == Summary:Report when CTEST_COVERAGE_COMMAND is not set Description: When CTEST_COVERAGE_COMMAND is not set, ctest reports: Problem running coverage on file: /home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/tests/CMakeFiles/comparePGXimages.dir/__/applications/common/opj_getopt.c.gcda Command produced error: No such file or directory .No such file or directory The output is confusing, it would be nice if cmCTestCoverageHandler::HandleGCovCoverage would test if std::string gcovCommand = this-CTest-GetCTestConfiguration(CoverageCommand); is empty or not. Additional Information: When looking at the debug log, it is clear that gcov is missing: Performing coverage: 1.32317e+09 * Run coverage for: /home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/applications/codec/CMakeFiles/image_to_j2k.dir Command: -l -p -o /home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/applications/codec/CMakeFiles/image_to_j2k.dir /home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/applications/codec/CMakeFiles/image_to_j2k.dir/image_to_j2k.c.gcda Output: Errors: No such file or directory == Issue History Date ModifiedUsername FieldChange == 2011-12-06 08:11 Mathieu MalaterreNew Issue == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Fwd: How to handle different cmake versions in extra-cmake-modules ?
On 12/6/2011 1:13 PM, Alexander Neundorf wrote: Does that look like it should cover all use cases, for peopling wanting to selectively use some things from e-c-m, and fearing that something would break if they simply would make everything available ? That proposal looks good to me. As an additional suggestion, I think you should always use an ECM version number so people get used to writing it. That way projects can ensure they get a compatible version of ECM: find_package(extra-cmake-modules 1.2 REQUIRED) -Brad -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Fwd: How to handle different cmake versions in extra-cmake-modules ?
On Tuesday 06 December 2011, Brad King wrote: On 12/6/2011 1:13 PM, Alexander Neundorf wrote: Does that look like it should cover all use cases, for peopling wanting to selectively use some things from e-c-m, and fearing that something would break if they simply would make everything available ? That proposal looks good to me. As an additional suggestion, I think you should always use an ECM version number so people get used to writing it. That way projects can ensure they get a compatible version of ECM: find_package(extra-cmake-modules 1.2 REQUIRED) Do you mean the version number should be enforced ? 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Fwd: How to handle different cmake versions in extra-cmake-modules ?
On 12/6/2011 1:37 PM, Alexander Neundorf wrote: On Tuesday 06 December 2011, Brad King wrote: That proposal looks good to me. As an additional suggestion, I think you should always use an ECM version number so people get used to writing it. That way projects can ensure they get a compatible version of ECM: find_package(extra-cmake-modules 1.2 REQUIRED) Do you mean the version number should be enforced ? Not necessarily, but it is good practice especially in this case. -Brad -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012610]: Uncaught exception in automoc logic on a specific CMakeLists.txt
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12610 == Reported By:Georg Rudoy Assigned To: == Project:CMake Issue ID: 12610 Category: CMake Reproducibility:sometimes Severity: crash Priority: normal Status: new == Date Submitted: 2011-12-06 16:50 EST Last Modified: 2011-12-06 16:50 EST == Summary:Uncaught exception in automoc logic on a specific CMakeLists.txt Description: When running CMake over the given CMakeLists.txt (see the attachment), it fails in cmQtAutomoc::SetupAutomocTarget(cmTarget*). The issue fails to reproduce with any other CMakeLists.txt I've tried (so there is no sane minimal reproducing example, sorry), but it always reproduces with this CMakeLists.txt. Steps to Reproduce: 1. Run CMake over the CMakeLists.txt from the attachment. 2. Get the uncaught exception. Additional Information: The whole app is available at git://github.com/0xd34df00d/leechcraft.git , the CMakeLists.txt in question is at /src/plugins/azoth/plugins/acetamide/ in that repo. The commit hash where this is observed is 9ce67f2958e695e6a616f14ab52568be99ae296e. It hasn't been observed earlier, since that CMakeLists.txt had no support for being ran over directly until this commit. I'm using gcc 4.5.3 and Qt 4.8 from their master. There are CMake output, backtrace and CMakeLists.txt in question in the attachment, as well as a couple of files it uses. == Issue History Date ModifiedUsername FieldChange == 2011-12-06 16:50 Georg RudoyNew Issue 2011-12-06 16:50 Georg RudoyFile Added: issue.tar.bz2 == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012611]: Missing CMAKE_INCLUDE_DIRECTORIES_BEFORE from documentation
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12611 == Reported By:Fraser Hutchison Assigned To: == Project:CMake Issue ID: 12611 Category: Documentation Reproducibility:N/A Severity: trivial Priority: low Status: new == Date Submitted: 2011-12-06 19:41 EST Last Modified: 2011-12-06 19:41 EST == Summary:Missing CMAKE_INCLUDE_DIRECTORIES_BEFORE from documentation Description: CMAKE_INCLUDE_DIRECTORIES_BEFORE is mentioned in the documentation for include_directories, but is not listed in the section Variables that Change Behavior == Issue History Date ModifiedUsername FieldChange == 2011-12-06 19:41 Fraser HutchisonNew Issue == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
