summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'remove-qmake-query'Brad King2010-06-152-30/+5
|\
| * Remove macro for querying qmake for qmake variables.Clinton Stimpson2010-06-122-30/+5
| | | | | | | | | | | | Remove last place for querying qmake values. Also removed internal macro to support querying qmake. Depends on findthreads-irix topic.
* | Merge branch 'findthreads-irix'Brad King2010-06-151-2/+4
|\ \
| * | Support pthreads on irix.Clinton Stimpson2010-06-121-2/+4
| | |
* | | Merge branch 'tru64-make-includes'Brad King2010-06-153-3/+9
|\ \ \
| * | | Tru64: Use full-path include directives in Makefiles (#10569)Brad King2010-06-143-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tru64's make(1) resolves relative paths in "include" directives with respect to the includer. This is inconsistent with all other known make tools. Note that this make tool treats the path literally so we cannot use our standard FULL path code which escapes spaces. Instead qualify the paths with $(CMAKE_BINARY_DIR) to avoid the problem.
* | | | Merge branch 'tru64-cmOStringStream-vtable'Brad King2010-06-154-1/+20
|\ \ \ \
| * | | | Tru64: Place cmOStringStream vtable uniquely (#10541)Brad King2010-06-104-1/+20
| |/ / / | | | | | | | | | | | | | | | | | | | | GCC places the vtable in the object implementing the first non-pure, non-inline virtual method. Since the symbol is not weak on Tru64, make the location unique by putting the destructor in a single object file.
* | | | Merge branch 'test-NoNewline-with-built-cmake'Brad King2010-06-151-1/+1
|\ \ \ \
| * | | | Run CTest.NoNewline test using built CMakeBrad King2010-06-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Even though this test is checking that the ctest running it can handle test output without newlines we should run the just-built CMake binary. This allows the MemCheck test mode to check the correct CMake.
* | | | | Merge branch 'fix-issue-10346'Brad King2010-06-151-1/+14
|\ \ \ \ \
| * | | | | Fix issue #10346. Error if SOURCE_DIR is empty.David Cole2010-06-091-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See http://public.kitware.com/Bug/view.php?id=10346. The proposed patch for the issue could not be applied as is because the SOURCE_DIR always exists for an ExternalProject_Add call by the time we get to the place to emit the potential error. The fix is to emit the error only if the source dir is empty. By which, I mean devoid of files and subdirectories. If SOURCE_DIR is used by itself, without any DOWNLOAD_COMMAND or repository info, then it implies that the SOURCE_DIR is ready to build as-is without need for a download step. Clearly, if it is empty, then it is not ready to build as is. So complain if the SOURCE_DIR is empty.
* | | | | | Merge branch 'cygwin-data-dirs'Brad King2010-06-152-14/+12
|\ \ \ \ \ \
| * | | | | | Fix CMake data and doc paths in Cygwin packageBrad King2010-06-092-14/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Override CMAKE_DOC_DIR and CMAKE_DATA_DIR cache entries on Cygwin early enough so the new values are used everywhere. Previously only some of the uses were overridden. Also set CPACK_PACKAGE_VERSION to the whole CMake_VERSION so that the Cygwin MANIFEST file goes in the proper path.
* | | | | | | Merge branch 'source-file-property-documentation'Brad King2010-06-152-29/+11
|\ \ \ \ \ \ \
| * | | | | | | Document scope of source file propertiesBrad King2010-06-092-29/+11
| | |/ / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | Also remove out-dated list of source file properties from the set_source_files_properties command.
* | | | | | | Merge branch 'mingw-response-files'Brad King2010-06-156-3/+23
|\ \ \ \ \ \ \
| * | | | | | | Use response file for objects on MinGW and MSYSBrad King2010-03-112-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Windows command lines are limited to about 32K so we need to use response files for linking very large lists of object files. See issue #10401.
| * | | | | | | Use platform variable for response file flagBrad King2010-03-112-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create platform variable "CMAKE_<LANG>_RESPONSE_FILE_LINK_FLAG" to specify an alternative to "@" for referencing response files. It applies specifically to response files with linker options. See issue #10401.
| * | | | | | | Use forward slashes for objects in response filesBrad King2010-03-113-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Response files are parsed by tools, not by shells. We teach cmLocalGenerator::Convert() a new "RESPONSE" output format and use it for objects listed in response files. It does not do special slash or MSYS root translation like the "SHELL" format does. This is necessary for GNU tools on Windows to understand response file content. See issue #10401.
* | | | | | | | KWSys Nightly Date StampKWSys Robot2010-06-151-1/+1
| | | | | | | |
* | | | | | | | KWSys Nightly Date StampKWSys Robot2010-06-141-1/+1
| | | | | | | |
* | | | | | | | KWSys Nightly Date StampKWSys Robot2010-06-131-1/+1
| |_|_|_|_|_|/ |/| | | | | |
* | | | | | | KWSys Nightly Date StampKWSys Robot2010-06-121-1/+1
| |_|_|_|_|/ |/| | | | |
* | | | | | KWSys: Teach Process to error on empty commandBrad King2010-06-112-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not try to execute a child with no command line. Previously this led to a silent hang.
* | | | | | KWSys: Process tree kill for SolarisBrad King2010-06-111-0/+3
| | | | | |
* | | | | | KWSys Nightly Date StampKWSys Robot2010-06-111-1/+1
| | | | | |
* | | | | | Merge branch 'suppress-sgi-warning-3968'Brad King2010-06-101-0/+1
|\ \ \ \ \ \ | |_|_|_|_|/ |/| | | | |
| * | | | | Suppress SGI MIPSpro warning 3968Brad King2010-06-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The warning appears everywhere we use static_cast to explicitly truncate an integer width. It appears in the form cc-3968 CC: WARNING File = ..., Line = ... implicit conversion of a 64-bit integral type to a smaller integral type (potential portability problem) static_cast<...>(...); ^ which is strange because a "static_cast" is not implicit. It also appears in system library code.
| * | | | | Mask out warnings on ferrari dashboard.David Cole2010-06-081-0/+1
| | |_|/ / | |/| | |
* | | | | KWSys: Configure DynamicLoader library prefix/suffixBrad King2010-06-103-88/+12
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | The DynamicLoader::LibPrefix and DynamicLoader::LibExtension methods previously hard-coded the module name components for each platform. Set them from the CMAKE_SHARED_MODULE_PREFIX and CMAKE_SHARED_MODULE_SUFFIX CMake variables instead. This ensures consistency in a program that uses these methods to construct the file names for its own modules.
* | | | KWSys Nightly Date StampKWSys Robot2010-06-101-1/+1
| |_|/ |/| |
* | | KWSys Nightly Date StampKWSys Robot2010-06-091-1/+1
|/ /
* | Merge branch 'sunCC-5.11-rpath-link'Brad King2010-06-082-1/+9
|\ \
| * | ChangeLog: Mention new Sun compiler supportBrad King2010-06-081-0/+1
| | |
| * | Fix rpath-link flag for SunPro C++ 5.11 on LinuxBrad King2010-06-071-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | Commit 82c081ba (Fix rpath-link flag for SunPro C++ on Linux, 2009-07-13) taught CMake to pass '-rpath-link' because SunPro C++ 5.9 does not support '-Wl,'. Now SunPro C++ 5.11 does not recognize the option without using '-Wl,'. Detect whether to use '-Wl,' based on the output of "sunCC -flags".
* | | KWSys Nightly Date StampKWSys Robot2010-06-081-1/+1
| | |
* | | ChangeLog: Update for today's topic mergesBrad King2010-06-071-0/+9
| | |
* | | Merge branch 'per-config-link-flags'Brad King2010-06-0713-45/+217
|\ \ \
| * | | Intel-specific workaround for LinkFlags testsBrad King2010-06-033-2/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Intel C compiler for Linux does not seem to reject any bad flags or object files on its link lines. Work around the problem by using a preprocessor #error directive to ensure that BADFLAG appears in the build output. This does not really achieve the purpose of the tests but it allows them to pass.
| * | | Borland-specific bad flag for LinkFlags testsBrad King2010-06-021-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | The Borland librarian actually creates a BADFLAG.obj when the object is missing the first time! This causes later tests to not reject it. Instead use a Borland-specific variation on the flag.
| * | | Better "bad" flag in LinkFlags testBrad King2010-06-011-6/+7
| | | | | | | | | | | | | | | | | | | | The Intel C Compiler for Linux ignores _BADFLAG_ when linking! Use a flag that looks like a missing object file to ensure its rejection.
| * | | Watcom: Use LINK_FLAGS and STATIC_LIBRARY_FLAGSBrad King2010-06-011-3/+3
| | | | | | | | | | | | | | | | Add the <LINK_FLAGS> rule variable in Watcom command lines.
| * | | Xcode: Archives use STATIC_LIBRARY_FLAGS, not LINK_FLAGSBrad King2010-05-281-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The LINK_FLAGS property is defined only for targets that really link. These include executables and shared libraries. For static libraries we define the STATIC_LIBRARY_FLAGS property. Teach the Xcode generator to make this distinction.
| * | | Add STATIC_LIBRARY_FLAGS_<CONFIG> property (#10768)Brad King2010-05-287-13/+77
| | | | | | | | | | | | | | | | This is a per-configuration version of STATIC_LIBRARY_FLAGS.
| * | | Test LINK_FLAGS and STATIC_LIBRARY_FLAGS (#10768)Brad King2010-05-284-0/+57
| | | | | | | | | | | | | | | | | | | | | | | | Add a LinkFlags test series to check that these properties work. Since no link flag is accepted everywhere we test for presence of flags by adding a bad flag and looking for the complaint in the test output.
| * | | Implement LINK_FLAGS_<CONFIG> in VS 10 generatorBrad King2010-05-281-0/+14
| | | | | | | | | | | | | | | | | | | | Add support for the per-config LINK_FLAGS property in VS 10. This was simply missing.
| * | | Fix LINK_FLAGS_<CONFIG> in VS 6 generatorBrad King2010-05-281-29/+45
| | | | | | | | | | | | | | | | Add the flags to the link step, not the compile step!
* | | | Merge branch 'ctest-update-git-submodule'Brad King2010-06-071-1/+1
|\ \ \ \
| * | | | Fix ctest_update log prefix for git submodule updateBrad King2010-06-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit 67277bac (Teach ctest_update about Git submodules, 2010-05-04) accidentally logged "git submodule update" with the prefixes "pull-out" and "pull-err". Fix it to use "submodule-out" and "submodule-err" instead.
generated by cgit v0.12 at 2025-09-10 12:47:37 (GMT)