| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
853ef717 Help: Clarify policy CMP0026 title
|
| |
| |
| |
| |
| |
| |
| | |
Clarify that the policy only applies to build targets and
not e.g. imported targets.
Suggested-by: Alan W. Irwin
|
|\ \
| | |
| | |
| | |
| | | |
1b03332e Help: Clarify that CMAKE_SIZEOF_VOID_P is specific to the target machine
|
| |/ |
|
|/
|
|
|
|
|
|
|
| |
The documentation of this variable in the CTest module is outdated
and has been superseded by the ctest(1) manual. In particular, the
latter mentions that it works with the Ninja generator as well as
makefile generators. Remove the documentation from the CTest module
and replace it with a link to the main variable documentation (which
already references the ctest(1) manual).
|
|\
| |
| |
| |
| |
| |
| |
| | |
b470d618 Help: Add notes for topic 'ExternalProject-genex'
0273ef14 ExternalProject: Allow generator expressions with LOG_* options (#15287)
7bd8cfb8 ExternalProject: Allow generator expressions in initial cache options
1cf43dcf Tests: Add case to cover ExternalProject with subdirectories
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
a61e0994 Help: Fix formatting of env var refs in ctest.1 manual
|
| |/ |
|
|/
|
|
|
| |
This has been implemented since commit v2.6.0~295 (Make find_library
test for the library file as named, 2008-02-06). Add the docs.
|
|\
| |
| |
| |
| |
| |
| | |
cd953bf7 Help: Add notes for topic 'cpack-rpm-refactored-file-listing'
76080c32 CPackRPM content listing refactor
152e9b32 CPackRPM package content list code move
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
66b641f4 Help: Add notes for topic 'add-GreenHills-MULTI-generator'
48004d9d Add a 'Green Hills MULTI' generator on Windows
051d8be1 cmLocalGenerator: Constify some cmTarget and cmGeneratorTarget arguments
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Green Hills MULTI is an IDE for embedded real-time systems. The IDE's
product page can be found here:
http://www.ghs.com/products/MULTI_IDE.html
It supports cross compiling on ARM, Intel x86, and other architectures
with various operating systems. The IDE exists on Linux and Windows
host systems, but CMake will currently only generate the project files
on Windows host systems.
|
| |/
|/|
| |
| | |
It uses the OUTPUT_NAME if set, not always the target name.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
84f06d0c FPHSA: Document REQUIRED_VARS recommendation (#15352)
a3ad275c FPHSA: Revise and format documentation
d1a6d15b FPHSA: Always populate the ExactCase_FOUND variable (#15412).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The UPPERCASE name was inconsistent with config-packages, the
find_dependency macro, and even FPHSA itself, which expects
components to be specified with names matching ExactCase.
The FOUND_VAR was only permitted to have two possible values, and
now both are set for compatibility. Document it as obsolete, and
adjust the code for the same. Users of the variable should just
remove it.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
885ab9ab VS: Drop reload macros for VS >= 10 (#11258,#14680)
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We never implemented them for VS 11 (2012), 12 (2013), or 14 (2015).
For VS 10 (2010) the reload macro does not work correctly when run from
inside a build launched through the IDE because stopping the build kills
the CMake that is driving the reload. Fortunately VS >= 10 know how to
reload the whole solution anyway.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
7b8e7c4a Deprecate Visual Studio 7 generator (.NET 2002)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Update documentation to mark the generator deprecated. Add a warning at
the end of generation plus an option to turn off the warning.
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
85c2626b Deprecate Visual Studio 6 generator
|
| |/ /
| | |
| | |
| | |
| | | |
Update documentation to mark the generator deprecated. Add a warning at
the end of generation plus an option to turn off the warning.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
9ac05683 Ninja: Drop 'experimental' label in documentation
|
| |/ /
| | |
| | |
| | |
| | | |
This generator is no longer experimental and has been fairly
mature for several releases already.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
The GITUpdateCustom and P4UpdateCustom options take only one command
line with all arguments as a ;-list, not a ;-list of multiple command
lines. Fix the incorrect documentation originally added by commit
v3.1.0-rc1~463^2 (Help: Document ctest dashboard client usage,
2014-05-30).
|
| |
| |
| |
| |
| |
| |
| | |
Allows specifying a libarchive defined archive format currently restricted to
7zip, gnutar, pax, paxr and zip.
The default is "paxr" (pax restricted).
|
|\ \
| |/
|/|
| |
| |
| |
| | |
882f48e5 Link libraries by full path even in implicit directories
318cd370 Help: Add link target for Find Modules section of cmake-developer.7
1535dcd8 Tests: Teach RunCMake to optionally merge command output to stdout
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When CMP0003 was first introduced we wanted to link all libraries by
full path. However, some projects had problems on platforms where
find_library would find /usr/lib/libfoo.so when the project really
wanted to link to /usr/lib/<arch>/libfoo.so and had been working by
accident because pre-CMP0003 behavior used -lfoo to link.
We first tried to address that in commit v2.6.0~440 (Teach find_library
to avoid returning library paths in system directories, 2008-01-23) by
returning just "foo" for libraries in implicit link directories. This
caused problems for projects expecting find_library to always return a
full path. We ended up using the solution in commit v2.6.0~366 (...
switch library paths found in implicit link directories to use -l,
2008-01-31). However, the special case for libraries in implicit link
directories has also proven problematic and confusing.
Introduce policy CMP0060 to switch to linking all libraries by full path
even if they are in implicit link directories. Explain in the policy
documentation the factors that led to the original approach and now to
this approach.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1975d53a Help: Add notes for topic 'emulator-property'
9160d6c2 TestGenerator: Add CROSSCOMPILING_EMULATOR support.
e942526b try_run: Use CMAKE_CROSSCOMPILING_EMULATOR.
579c4bec Properties: Add CROSSCOMPILING_EMULATOR target property.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Prefix test commands with the CROSSCOMPILING_EMULATOR property
for target executables. This allows test suites to be run on the host
when crosscompiling.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the CMAKE_CROSSCOMPILING_EMULATOR variable is defined, and
CMAKE_CROSSCOMPILING is TRUE, then use CMAKE_CROSSCOMPILING_EMULATOR to run
the try_run executables. This prevents the need to populate
TryRunResults.cmake when cross compiling.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add CROSSCOMPILING_EMULATOR target property for executables. This is used by
subsequent patches to run exectuables created for the target system when
crosscompiling. The property is initialized by the
CMAKE_CROSSCOMPILING_EMULATOR variable when defined.
|
|/ /
| |
| |
| |
| |
| |
| | |
Extend sentences in other documentation linking to this manual to
say that it has a list of supported compilers.
Co-Author: Brad King <brad.king@kitware.com>
|
|\ \
| |/
|/|
| |
| | |
d2240390 Help: Add notes for topic 'gcov-module-coverage-exclude'
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
6f82b5e8 Help: Link to properties in set_tests_properties.
66f5af29 Help: Link to properties in set_directory_properties docs.
f7dd3f7c Help: Add link in set_source_files_properties command docs.
3b256173 Help: Shorten too-long title marker.
8fc3a2fb Help: Add references to cmake-property sections.
|
| | |
| | |
| | |
| | | |
Remove help for specific properties to their own help pages.
|
| | |
| | |
| | |
| | | |
Remove claim that CMake will report an error for unknown properties.
|
| | |
| | |
| | |
| | |
| | | |
Remove claim about unrecognized properties being ignored. Such
properties can be retrieved later by the user.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
659896d3 Help: Revise target_link_libraries command documentation
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Organize the documentation into subsections to separate the signatures.
Refactor the discussion of allowed link items into bullet points and
expand into more detail on each.
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
01a9ab0d VS: Add support for XAML source files
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
XAML files are by default of type Page in the vcxproj and can be
overriden by setting the VS_XAML_TYPE property. The .cpp and .h file
of the same name are automatically added as depending on the XAML file.
New VSXaml test builds a basic XAML WindowsStore 8.1 app with VS2013.
|