summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'upstream-kwsys' into import-KWSys-subtreeBrad King2012-10-316-133/+657
|
* KWSys: Submit dashboard builds to PublicDashboardBrad King2012-10-011-1/+1
| | | | | | CMake's test suite includes a dashboard build of KWSys directly out of the CMake source tree. Upstream KWSys switched to a dedicated dashboard but CMake's test should still submit to the PublicDashboard project.
* Merge branch 'upstream-kwsys' into import-KWSys-subtreeBrad King2012-10-016-339/+1094
|
* Merge topic 'KWSys-hashtable-old-gcc'David Cole2012-06-121-1/+1
|\ | | | | | | | | 4f170e2 KWSys: Fix hashtable prime list on g++ 2.9 (#13273)
| * KWSys: Fix hashtable prime list on g++ 2.9 (#13273)Daniel R. Gomez2012-06-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | Building CMake with g++ 2.9-aix51-020209 on an AIX 5.3 system gives: cmsys/hashtable.hxx: In function `const long unsigned int *cmsys::get_stl_prime_list ()': cmsys/hashtable.hxx:399: warning: sorry: semantics of inline function static data `const long unsigned int _stl_prime_list[31]' are wrong (you'll wind up with multiple copies) cmsys/hashtable.hxx:399: warning: you can work around this by removing the initializer Give get_stl_prime_list internal linkage.
* | CMake Nightly Date StampKitware Robot2012-06-121-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-111-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-101-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-091-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-081-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-071-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-061-1/+1
|/
* Merge topic 'Ninja-EXPORT_COMPILE_COMMANDS'David Cole2012-06-056-15/+102
|\ | | | | | | | | | | | | | | | | 3545645 Exclude the CompileCommandOutput test on WIN32. fbaddf4 Escape the source file to be compiled if required. db839be Make the CMAKE_EXPORT_COMPILE_COMMANDS option work with Ninja. 8778357 Add newline to the output. 2c04bc0 Move the EscapeJSON method to a sharable location.
| * Escape the source file to be compiled if required.Stephen Kelly2012-06-041-1/+4
| | | | | | | | | | Whitespaces in paths can otherwise cause invalid command lines to be generated.
| * Make the CMAKE_EXPORT_COMPILE_COMMANDS option work with Ninja.Stephen Kelly2012-06-043-0/+78
| |
| * Move the EscapeJSON method to a sharable location.Stephen Kelly2012-06-043-15/+21
| |
* | Merge topic 'vcexpress-no-folder'David Cole2012-06-052-0/+9
|\ \ | | | | | | | | | | | | a0700ba VC Express doesn't support folders, ignore USE_FOLDER property
| * | VC Express doesn't support folders, ignore USE_FOLDER propertyPeter Kuemmel2012-06-022-0/+9
| | |
* | | CMake Nightly Date StampKitware Robot2012-06-051-1/+1
| |/ |/|
* | CMake Nightly Date StampKitware Robot2012-06-041-1/+1
| |
* | CMake Nightly Date StampKitware Robot2012-06-031-1/+1
|/
* CMake Nightly Date StampKitware Robot2012-06-021-1/+1
|
* CMake Nightly Date StampKitware Robot2012-06-011-1/+1
|
* CMake Nightly Date StampKitware Robot2012-05-311-1/+1
|
* CMake Nightly Date StampKitware Robot2012-05-301-1/+1
|
* Merge topic 'cpack-nsis-menu-links-adapted'David Cole2012-05-291-2/+2
|\ | | | | | | | | cfc11f9 CPack: Fixed incorrect error log for CPACK_NSIS_MENU_LINKS.
| * CPack: Fixed incorrect error log for CPACK_NSIS_MENU_LINKS.Fraser Hutchison2012-05-281-2/+2
| | | | | | | | | | | | This was a pull request: https://github.com/Kitware/CMake/pull/5 Signed-off-by: Eric NOULARD <eric.noulard@gmail.com>
* | Merge topic 'IMPORTED_LOCATION_CONFIG-docs'David Cole2012-05-291-3/+3
|\ \ | | | | | | | | | | | | bdc6e32 Update the docs of IMPORTED_LOCATION_CONFIG to match the code.
| * | Update the docs of IMPORTED_LOCATION_CONFIG to match the code.Stephen Kelly2012-05-251-3/+3
| | |
* | | Merge topic 'kwsys-no-win32-environ-decl'David Cole2012-05-291-4/+0
|\ \ \ | | | | | | | | | | | | | | | | 0fbaa63 KWSys: Remove unused environ declaration from SystemTools
| * | | KWSys: Remove unused environ declaration from SystemToolsBrad King2012-05-231-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit "KWSys: Fix SystemTools environment memory handling" (2012-04-26) added a _WIN32 case inside !KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H to dllimport the "environ" global. Howver, KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H is true on every Windows toolchain we support so the case is never reached. Furthermore, even if it were reached the use of dllimport is incorrect because the toolchain might not be compiling with a dynamic runtime library. Remove the unused incorrect line and supporting conditionals.
* | | | CMake Nightly Date StampKitware Robot2012-05-291-1/+1
| | | |
* | | | CMake Nightly Date StampKitware Robot2012-05-281-1/+1
| | | |
* | | | CMake Nightly Date StampKitware Robot2012-05-271-1/+1
| | | |
* | | | CMake Nightly Date StampKitware Robot2012-05-261-1/+1
| |_|/ |/| |
* | | CMake Nightly Date StampKitware Robot2012-05-251-1/+1
| | |
* | | Merge topic 'fortran-include-angle'David Cole2012-05-246-653/+767
|\ \ \ | | | | | | | | | | | | | | | | ad21079 Fortran: Follow <>-style includes (#13239)
| * | | Fortran: Follow <>-style includes (#13239)Brad King2012-05-226-653/+767
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortran sources that pass through the C preprocessor may use #include "header" syntax or #include <header> syntax. CMake already follows the former. Teach it to follow the latter.
* | | | Merge topic 'CPack-activateRPM-DEB-onMacOS'David Cole2012-05-244-30/+108
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | 801ea70 Calm down Borland compiler warning about "always true" 2a34b57 CPack allow RPM and DEB generator to be used on OSX.
| * | | | Calm down Borland compiler warning about "always true"Eric NOULARD2012-05-211-0/+4
| | | | |
| * | | | CPack allow RPM and DEB generator to be used on OSX.Eric NOULARD2012-05-204-30/+104
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | More generally add the check for possible generator "activation" at runtime depending on a generator specific check. The dynamic behavior is currently implemented only for MacOS and should be fully backward compatible for other system. Inspired-By Tom Hughes <tomtheengineer@gmail.com>
* | | | | Merge topic 'CPackNSIS-warnDESTDIRandABSOLUTE'David Cole2012-05-247-2/+184
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4986d52 Use CPACK_xxx and CMAKE_xxx in a consistent way. f90223c Fix KWStyle warning 47f0dbd CPack add necessary check to detect/warns/error on ABSOLUTE DESTINATION 6ba055b CPack add easy possibility to warn about CPACK_SET_DESTDIR
| * | | | | Use CPACK_xxx and CMAKE_xxx in a consistent way.Eric NOULARD2012-05-204-13/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CMAKE_xxx vars are now used in the CMake-generated cmake_install.cmake script while CPACK_xxx equivalent vars are used from within CPack. CPack is responsible for getting/forwarding definitions of CPACK_xxxx var corresponding to CMAKE_xxxx when invoking CMake-generated install scripts. As a consequence: CMAKE_ABSOLUTE_DESTINATION_FILES CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION may be used from outside CPack as well. e.g. cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=1 -P cmake_install.cmake works as expected.
| * | | | | Fix KWStyle warningEric NOULARD2012-05-151-1/+2
| | | | | |
| * | | | | CPack add necessary check to detect/warns/error on ABSOLUTE DESTINATIONEric NOULARD2012-05-146-1/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The [usually] wrong usage of absolute DESTINATION in INSTALL rules keeps popping-up on the ML. We shall have some way to: 1) easily detect it. 2) forbids this for some CPack generator like NSIS In fact it should certainly be forbidden for *any* generators when used on Windows but we may implements that on top of the current patch. The patch ask the task to the generated cmake_install.cmake scripts. Those scripts are a little bit more complicated with that but iff there are absolute DESTINATION. This cost nothing if relative DESTINATION are used. Two new vars are introduced (and documented to handle that): CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION and CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION
| * | | | | CPack add easy possibility to warn about CPACK_SET_DESTDIREric NOULARD2012-05-144-1/+63
| | | | | | | | | | | | | | | | | | | | | | | | CPackNSIS will only warn but sooner or later it should error out
* | | | | | Merge topic 'MakeDefaultInstallComponentNameConfigurable'David Cole2012-05-248-77/+105
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b71e731 -add docs for ${CMAKE_INSTALL_DEFAULT_COMPONENT_NAME} 7ced073 make default install component name configurable b6fba35 -strip trailing whitespace
| * | | | | | -add docs for ${CMAKE_INSTALL_DEFAULT_COMPONENT_NAME}Alex Neundorf2012-05-141-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Alex
| * | | | | | make default install component name configurableAlex Neundorf2012-05-147-23/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until now an unnamed component was always named "Unspecified". Now this name is taken from the new cmake variable CMAKE_INSTALL_DEFAULT_COMPONENT_NAME, which is initialized to "Unspecified". But it can now be set to something project-specific, per directory Alex
| * | | | | | -strip trailing whitespaceAlex Neundorf2012-05-136-54/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Alex
generated by cgit v0.12 at 2025-02-10 13:04:05 (GMT)