- Feb 11, 2015
-
-
Brad King authored
-
Brad King authored
-
Brad King authored
The project has moved from <http://www.coin3d.org/> to <https://bitbucket.org/Coin3D/coin/wiki/Home>. Simply drop the out-dated link. Few find modules have links to the project sites. Anyone looking to use a given find module likely already knows about the project it finds and can use a search engine to find its homepage.
-
The file(GLOB_RECURSE) call added by commit 3ec02547 (CPackRPM: Allow multiple path relocation prefixes for one package, 2015-01-21) should not follow directory symlinks, so make sure CMP0009 is set to NEW.
-
- Feb 10, 2015
-
-
Brad King authored
-
Link to 'CTEST_TEST_TIMEOUT', not 'CTEST_TESTING_TIMEOUT'.
-
Brad King authored
-
-
Brad King authored
-
Brad King authored
-
Fix typo in logic added by commit 3ec02547 (CPackRPM: Allow multiple path relocation prefixes for one package, 2015-01-21).
-
Fix a logic typo introduced by commit v3.1.0-rc1~781^2 (Generalize cmCustomCommandGenerator to more fields, 2014-03-10).
-
- Feb 06, 2015
-
-
Brad King authored
-
Brad King authored
Resolve conflict in Source/CMakeLists.txt by taking both changes.
-
Brad King authored
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>
-
Brad King authored
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.
-
- Feb 05, 2015
-
-
Brad King authored
-
Brad King authored
Release versions do not have the development topic section of the CMake Release Notes index page.
-
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
-