- Feb 10, 2015
-
-
- Feb 05, 2015
-
-
af8d1c17 Help: Rename 3.x.0 release notes to 3.x
-
Brad King authored
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.
-
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.
-
219797e4 Help: Revise try_compile and try_run documentation (#15358)
-
ecaee7ca CPack: Fix NSIS default 64-bit Windows install directory (#14211)
-
Brad King authored
-
-
-
Brad King authored
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>
-
Brad King authored
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.
-
Brad King authored
-
Kitware Robot authored
-
- Feb 04, 2015
-
-
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.
-
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.
-
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.
-
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.
-
-
Brad King authored
Rewrite the documentation using better reStructuredText markup constructs. Clarify interaction of options like LINK_LIBRARIES and CMAKE_FLAGS.
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Brad King authored
When targeting Windows with a 64-bit architecture, use "$PROGRAMFILES64" to get the Program Files folder. Use CMAKE_SIZEOF_VOID_P to check for the architecture size instead of CMAKE_CL_64 because the latter is not defined for all compilers. Inspired-by:
Hugh Sorby <h.sorby@auckland.ac.nz> Inspired-by:
İsmail Dönmez <ismail@donmez.ws>
-
Brad King authored
-
dea42d92 install: Fix regression in default configuration selection
-
467f5bcc MSVC: Fix initialization of RelWithDebInfo shared library link flags (#15385)
-
2fed8e17 QtAutogen: Issue error message with origin file (#15342).
-
809a5a5e Help: Add notes for topic 'CTestCoverageCollectGCOV-refinements' 03c0812c CTestCoverageCollectGCOV: Fix handling of international characters 8caa4e72 CTestCoverageCollectGCOV: Add test case 5c828cc8 CTestCoverageCollectGCOV: Allow custom flags to gcov 30cb628e CTestCoverageCollectGCOV: Fix handling of large file counts
-
Brad King authored
-
Kitware Robot authored
-
- Feb 03, 2015
-
-
Stephen Kelly authored
-
Brad King authored
-
Brad King authored
Initialize CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO_INIT from the value of CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO_INIT rather than the one for the DEBUG configuration. This typo has been present since the logic was first added in commit 36db4508 (ENH: fix up several problems with new stuff, 2002-11-11). Reported-by:
Gunnar Roth <gunnar.roth@gmx.de>
-
Brad King authored
-
The refactoring in commit v3.1.0-rc1~812^2~16 (stringapi: Pass configuration names as strings, 2014-02-09) broke the code path in cmLocalGenerator::GenerateInstallRules that intends to pick a default install configuration for multi-config generators. Fix the logic to select an empty default configuration only when using a single-config generator whose CMAKE_BUILD_TYPE is not set. Inspired-by:
Roman Wüger <roman.wueger@gmx.at> Reported-by:
NoRulez <norulez@me.com>
-
Brad King authored
When loading the list of target support directories, read the file with UTF-8 encoding since that is what CMake writes into the file. This allows us to support international characters in the path to the build tree containing the target support directories.
-
-
Add a GCOV_OPTIONS option to allow specification of custom flags. In ctest_coverage gcov support, if you set CTEST_COVERAGE_EXTRA_FLAGS, they get put on the command line before the -o. In this case we remove the -b and replace it with GCOV_OPTIONS. All other arguments remain the same.
-