The latter fits more consistently with other third party integration
files.

The directory contains auxiliary support files for integration with
other tools, not documentation.

Drop the "cmake version ..." line from the top of usage and text help
formats.  Print it only when requested with --version or similar option.

All the other --help-<item> options have a corresponding option
--help-<item>-list.  Add one for --help-policy.

Factor the CMAKE_DATA_DIR, CMAKE_DOC_DIR, and CMAKE_MAN_DIR selection
out of CMakeLists.txt and into a Source/CMakeInstallDestinations.cmake
script.  Load the script from the original location of the code.

Cache the destination values as empty strings so we know if the user
sets them explicitly.  If not, then compute defaults based on the
platform and full CMake version string.  By not caching the versioned
defaults, we can change them in a single build tree as the version
changes.

Remove duplication of the install destination defaults from the
bootstrap script.  Cache empty defaults there too.  Parse from the CMake
code the default values to report in the help output.  Keep the CMake
code in a structured format to make this reliable.

Move logic to compute CMake_VERSION out of the top-level CMakeLists.txt
file to a dedicated Source/CMakeVersionCompute.cmake module and include
it from the original location.  This will allow it to be re-used.

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

eec7834e list: Fix docs for APPEND to show that elements are optional

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

2e6cadde CPackWiX: allow user supplied extra sources, objects and libraries

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

3a4a7482 CPackWiX: generate deterministic ids for directories, components and files

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

e4e5b28c cmTarget: Deprecate the LOCATION target property with a policy.

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

50762188 FindCUDA: Fix NPP library search for CUDA 5.5

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

3507d5af Deprecate COMPILE_FLAGS target property.

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

a4263c9f export(): Handle multiple dependent export sets.
66b290e7 export(): Process the export() command at generate time.
5fe5c324 export(): Set a Makefile on the cmExportBuildFileGenerator.
e3835558 cmExportInstallFileGenerator: Fix comment to match reality.

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

af1f6987 CMP0024: Store the fact of included export in global generator.

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

920ffbf5 Require CMake 2.8.4 or greater to build CMake

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

2e13c362 OS X: Encode -F framework search flag in per-language platform variable

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

617ee7c5 Add a test for SYSTEM headers in INTERFACE libraries.

Stephen Kelly authored 11 years ago and Brad King committed 11 years ago

This allows the use of the $<TARGET_FILE:...> generator expression as a
replacement for the use of the LOCATION target property.  The use of the
LOCATION target property is now deprecated for in-build targets.

Also drop other checks for older CMake versions:

* Simplify cmake_set_target_folder macro.
* Use find_package(LibArchive) unconditionally.
* Simplify condition for running testVisualStudioSlnParser test.
* Convert two macros to functions.
* Unconditionally run the CTestTestRerunFailed test.

Роман Донченко authored 11 years ago and Brad King committed 11 years ago

list(APPEND) has been able to append nothing since commit a06dcdba
(Allow LIST(APPEND) command to append nothing, 2008-01-16) but the
documentation still used to imply that at least one argument is
required.

The final location and name of a build-target is not determined
until generate-time. However, reading the LOCATION property from
a target is currently allowed at configure time. Apart from creating
possibly-erroneous results, this has an impact on the implementation
of cmake itself, and prevents some major cleanups from being made.

Disallow reading LOCATION from build-targets with a policy. Port some
existing uses of it in CMake itself to use the TARGET_FILE generator
expression.

Vladislav Vinogradov authored 11 years ago and Brad King committed 11 years ago

In CUDA 5.5 NPP was divided onto 3 separate libraries: nppc, npps, nppi.

It is succeeded by COMPILE_OPTIONS, which supports generator
expressions, is a list rather than a string, and is properly
escaped.

The export-sets topic, merged in commit 49c7b649 (Merge topic
'export-sets', 2012-10-01) changed install(EXPORT) to allow
exporting targets whose dependents are exported separately
to different locations. Doing the same for export() was not
possible because the export() command was executed at
configure-time.

Now that export() is also executed at generate-time, make it
possible to export to multiple dependent export sets.

Make the API for adding targets string based so that it can easily
use cmGeneratorTarget.

Teach the cmIncludeCommand to generate the exported file at
configure-time instead if it is to be include()d.

The RunCMake.ExportWithoutLanguage test now needs a dummy header.h
file as expected error from export() is now reported after the
missing file error.

This is better than the cmCommand, because the lifetime of that is
not as useful, and it is only used to report an error anyway.

In the next commit, the cmExportBuildFileGenerator will outlive the
cmCommand.

Compilers for languages other than C and C++ on OS X may not understand
the -F framework search flag.  Create a new platform information
variable CMAKE_<LANG>_FRAMEWORK_SEARCH_FLAG to hold the flag, and set it
for C and CXX lanugages in the Platform/Darwin module.

Reported-by: Vittorio Giovara <vittorio.giovara@gmail.com>

It was copied from cmExportBuildFileGenerator.

Storing it in the makefile means that the policy does not trigger
when include and export are in differing directories.

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

7f459a66 Xcode: Teach BuildDepends test that Xcode >= 5 needs no help

Brad King authored 11 years ago and Kitware Robot committed 11 years ago

dcf1b645 OS X: Set CMake.app bundle Info.plist fields (#11694)