summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'makefile-progress-improvements'Brad King2015-02-1012-125/+170
|\ | | | | | | | | | | | | | | | | | | 63668954 Help: Add notes for topic 'makefile-progress-improvements' ae775fe8 Makefile: Change link step message color to bold green 7bb50e4a Makefile: Add progress to link step messages c6ada827 Makefile: Print all color escape sequences before newline 8521fdf5 Makefile: Fix output during parallel builds (#12991) 69ac6d27 bootstrap: Enable color Makefile output
| * Help: Add notes for topic 'makefile-progress-improvements'Brad King2015-02-071-0/+7
| |
| * Makefile: Change link step message color to bold greenBrad King2015-02-071-1/+1
| | | | | | | | Avoid displaying red messages when no error has occurred.
| * Makefile: Add progress to link step messagesBrad King2015-02-072-2/+10
| |
| * Makefile: Print all color escape sequences before newlineBrad King2015-02-061-3/+9
| | | | | | | | Ensure that the escape sequences do not leak across lines.
| * Makefile: Fix output during parallel builds (#12991)Brad King2015-02-066-93/+133
| | | | | | | | | | | | | | | | | | | | Replace use of separate "cmake -E cmake_progress_report" and "cmake -E cmake_echo_color" commands to report the progress and message portions of build output lines with --progress-* options to the latter to print everything with a single command. The line buffering of the stdout FILE stream should cause the whole line to be printed with one atomic write. This will avoid inter-mixing of line-wise messages from different processes during a parallel build.
| * bootstrap: Enable color Makefile outputBrad King2015-02-055-26/+10
| | | | | | | | | | | | Build the needed infrastructure during bootstrap in order to allow "cmake -E cmake_echo_color" to be used unconditionally during generation.
* | Merge topic 'try_compile-quote-module-path'Brad King2015-02-101-1/+1
|\ \ | | | | | | | | | | | | 220c427e try_compile: Quote the content of CMAKE_MODULE_PATH to allow for spaces
| * | try_compile: Quote the content of CMAKE_MODULE_PATH to allow for spacesNils Gladitz2015-02-091-1/+1
| | |
* | | Merge topic 'no-global-setlocale'Brad King2015-02-109-12/+39
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 0f870234 Merge branch 'backport-no-global-setlocale' into no-global-setlocale cd408d93 Add setlocale() calls around use of libarchive APIs (#14934, #15377) 87be2e14 Do not call setlocale() globally in CMake applications (#15377)
| * \ \ Merge branch 'backport-no-global-setlocale' into no-global-setlocaleBrad King2015-02-069-12/+39
| |\ \ \ | | | | | | | | | | | | | | | Resolve conflict in Source/CMakeLists.txt by taking both changes.
| | * | | Add setlocale() calls around use of libarchive APIs (#14934, #15377)Brad King2015-02-064-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The libarchive APIs use nl_langinfo(CODESET) for iconv so they need the locale to be set for LC_CTYPE. However, the rest of CMake does not define any behavior for non-ASCII character classification/conversion so we do not want to setlocale() globally. Add a RAII class to save, set, and restore the locale around calls to libarchive APIs. Inspired-by: Clinton Stimpson <clinton@elemtech.com>
| | * | | Do not call setlocale() globally in CMake applications (#15377)Brad King2015-02-065-12/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Revert the changes made by commit v3.1.0-rc1~406^2~1 (Encoding: Add setlocale() to applications, 2014-05-30) and commit v3.1.0-rc1~406^2 (Encoding: Change to only set LC_CTYPE, 2014-06-11), and other setlocale calls added later in their spirit. CMake has not been taught how to deal with non-C locales everywhere. We do not define any functionality for character conversions for non-ASCII strings. Another solution will be needed to address the original problem motivating addition of setlocale() calls.
* | | | | Merge topic 'add-CheckFortranCompilerFlag'Brad King2015-02-106-2/+84
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1814cf74 Help: Add notes for topic 'add-CheckFortranCompilerFlag' 54e900ab CheckFortranCompilerFlag: Add test case 393a45e2 CheckFortranCompilerFlag: Add module to check Fortran flag existence
| * | | | | Help: Add notes for topic 'add-CheckFortranCompilerFlag'Brad King2015-02-051-0/+6
| | | | | |
| * | | | | CheckFortranCompilerFlag: Add test caseBrad King2015-02-051-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Extend the FortranOnly test with a case covering this module.
| * | | | | CheckFortranCompilerFlag: Add module to check Fortran flag existenceNicolas Bock2015-02-054-2/+71
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | Copy the CheckCCompilerFlag module and replace 'C' with 'Fortran'. Also update the common patterns module to match some Fortran compiler messages.
* | | | | Merge topic 'xcode-flags-per-language'Brad King2015-02-101-76/+79
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d2fe4c42 cmGlobalXCodeGenerator: Rename variable 'lang' => 'llang' de63ff48 Xcode: Generate Intel Fortran compiler flags in project files 9924486f Xcode: Refactor generation of per-language compiler flags
| * | | | | cmGlobalXCodeGenerator: Rename variable 'lang' => 'llang'Brad King2015-02-061-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In CreateBuildSettings the variable holds the linker language. Use a more distinctive variable name.
| * | | | | Xcode: Generate Intel Fortran compiler flags in project filesBrad King2015-02-061-0/+5
| | | | | |
| * | | | | Xcode: Refactor generation of per-language compiler flagsBrad King2015-02-061-71/+69
| |/ / / /
* | | | | Merge topic 'FindBoost-per-config-libraries'Brad King2015-02-102-49/+112
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 39e0aa53 Help: Add notes for topic 'FindBoost-per-config-libraries' 892b854f FindBoost: Search for debug and release libraries separately (#15364)
| * | | | | Help: Add notes for topic 'FindBoost-per-config-libraries'Brad King2015-02-051-0/+5
| | | | | |
| * | | | | FindBoost: Search for debug and release libraries separately (#15364)Gunther Laure2015-02-051-49/+107
| |/ / / / | | | | | | | | | | | | | | | | | | | | Split Boost_LIBRARY_DIR into Boost_LIBRARY_DIR_[RELEASE,DEBUG] to allow libraries to be grouped into per-config directories.
* | | | | CMake Nightly Date StampKitware Robot2015-02-101-1/+1
| |_|_|/ |/| | |
* | | | CMake Nightly Date StampKitware Robot2015-02-091-1/+1
| | | |
* | | | CMake Nightly Date StampKitware Robot2015-02-081-1/+1
| | | |
* | | | CMake Nightly Date StampKitware Robot2015-02-071-1/+1
| | | |
* | | | CMake Nightly Date StampKitware Robot2015-02-061-1/+1
|/ / /
* | | Begin post-3.2 developmentBrad King2015-02-053-2/+11
| | |
* | | Merge branch 'release'Brad King2015-02-054-13/+4
|\ \ \ | |/ / |/| |
| * | CMake 3.2.0-rc1 version updateBrad King2015-02-052-4/+4
| | |
| * | Help: Drop development topic notes to prepare releaseBrad King2015-02-052-9/+0
|/ / | | | | | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* | Merge topic 'rename-release-notes'Brad King2015-02-054-12/+12
|\ \ | | | | | | | | | | | | af8d1c17 Help: Rename 3.x.0 release notes to 3.x
| * | Help: Rename 3.x.0 release notes to 3.xBrad King2015-02-054-12/+12
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | In commit v3.0.0-rc1~9 (Help: Rename 3.0 release notes to 3.0.0, 2014-02-19) we anticipated the possibility of bugfix-only release notes. However, in practice we have no release notes for bug fix releases because we do not cover bug fixes in release notes at all, only new features. Instead we've been updating the feature-level release notes document in bug fix releases, treating errors in the document as bugs. It makes more sense to maintain release notes at the feature-release level, so rename the documents accordingly. Also update the document titles and intro text to refer only to feature versions and not bugfix versions.
* | Merge topic 'doc-3.2-relnotes'Brad King2015-02-0553-341/+283
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | d81bbc3f Help: Add 3.2 release note for AUTORCC dependency tracking 0f38d9c2 Help: Add 3.2 release notes for file(GENERATE) features 0f580e8e Help: Organize and revise 3.2 release notes e08a78dc Help: Consolidate 3.2 release notes 3a4381b6 Help: Add link target to cmake-language.7 encoding section
| * | Help: Add 3.2 release note for AUTORCC dependency trackingStephen Kelly2015-02-051-0/+4
| | |
| * | Help: Add 3.2 release notes for file(GENERATE) featuresStephen Kelly2015-02-051-0/+7
| | |
| * | Help: Organize and revise 3.2 release notesBrad King2015-02-051-154/+174
| | | | | | | | | | | | | | | | | | | | | | | | Add section headers similar to the 3.1 release notes and move each individual bullet into an appropriate section. Revise and consolidate some bullets covering related areas. Co-Author: Stephen Kelly <steveire@gmail.com>
| * | Help: Consolidate 3.2 release notesBrad King2015-02-0552-341/+250
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.2.0.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand.
| * | Help: Add link target to cmake-language.7 encoding sectionBrad King2015-02-051-0/+2
| | |
* | | Merge topic 'update-docs'Brad King2015-02-054-3/+6
|\ \ \ | | | | | | | | | | | | | | | | | | | | f9839c49 Help: Document build targets automatically added to console pool. 44d6f3ce Help: Add some cross-linking.
| * | | Help: Document build targets automatically added to console pool.Stephen Kelly2015-02-041-0/+3
| | | |
| * | | Help: Add some cross-linking.Stephen Kelly2015-02-043-3/+3
| |/ /
* | | Merge topic 'fix-C-standard-features'Brad King2015-02-0516-21/+198
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fb3487a9 Features: Fix C90 feature detection. 6027798a Features: Allow setting standard dialect below the default. 9d767810 Features: Populate CMAKE_<LANG>_STANDARD_DEFAULT only for supported compilers. 72537e44 Features: Add dialect compile flags only if default is known. 82c9d686 AppleClang: Remove redundant UNIX condition.
| * | | Features: Fix C90 feature detection.Stephen Kelly2015-02-048-3/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This bug caused c_function_prototypes to not be recorded at configure time when compiling with -std=gnu99 or similar. In the case of feature recording, that was not a problem, because the logic in CMakeDetermineCompileFeatures.cmake currently assumes that a feature present for an earlier standard is present for a later standard. However, the detection strings are also used in WriteCompilerDetectionHeader, so the feature macro has been defined to '0' when using a later language dialect. Fix that by not checking the existence of the __STDC_VERSION__ macro at all when detecting C90 features.
| * | | Features: Allow setting standard dialect below the default.Stephen Kelly2015-02-041-1/+15
| | | | | | | | | | | | | | | | | | | | If the requested standard dialect is older than the default dialect then we must use a flag because we cannot decay to a newer standard.
| * | | Features: Populate CMAKE_<LANG>_STANDARD_DEFAULT only for supported compilers.Stephen Kelly2015-02-047-8/+21
| | | | | | | | | | | | | | | | | | | | | | | | If no compiler feature information is known for a given compiler version, do not set a language standard default either. The two settings must be recorded consistently.
| * | | Features: Add dialect compile flags only if default is known.Stephen Kelly2015-02-041-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The CMAKE_<LANG>_STANDARD_DEFAULT variable indicates whether the compiler has any notion of standard levels and that CMake knows about them. If no language standard levels are available, skip all logic to attempt to add a flag for the level. Also fail with an internal error if a bad default value is set.
| * | | AppleClang: Remove redundant UNIX condition.Stephen Kelly2015-02-042-2/+2
| | | |
generated by cgit v0.12 at 2025-01-09 08:58:28 (GMT)