| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes: #17997
|
|
|
|
|
| |
This adds VS_DEBUGGER_COMMAND_ARGUMENTS and VS_DEBUGGER_ENVIRONMENT as
well as allowing VS_DEBUGGER_* to use generator expressions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This family enable to manage link flags
Three new properties:
* directory property: LINK_OPTIONS
* target properties: LINK_OPTIONS and INTERFACE_LINK_OPTIONS
Two new commands
* add_link_options(): to populate directory property
* target_link_options(): to populate target properties
Fixes: #16543
|
|
|
|
| |
Fixes: #16365
|
|
|
|
| |
Fixes: #17955
|
| |
|
|
|
| |
No functional changes, just docs, comments and error messages.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
eb80af9093 Drop Visual Studio 8 2005 generator
e7af91d026 Tests: Remove unused file from Tutorial Step7 test
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1901
|
| |
| |
| |
| | |
This generator has been deprecated since CMake 3.9. Remove it.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
df535ad846 Add CMAKE_FOLDER variable to initialize FOLDER target property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1896
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This can be used for example to organize all following targets into one
Visual Studio folder:
set(CMAKE_FOLDER Libraries)
add_subdirectory(libA)
add_subdirectory(libB)
set(CMAKE_FOLDER Executables)
add_subdirectory(progA)
Another possibility is using the current directory name for all
following targets in subdirectories:
get_filename_component(dirname "${CMAKE_CURRENT_SOURCE_DIR}" NAME)
string(APPEND CMAKE_FOLDER "/${dirname}")
|
|/
|
|
| |
Issue: #17849
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
6db61f0725 Export: allow exporting of additional properties
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1834
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change introduces an additional property that may be set on a
target to allow additional properties to be exported. Normally only a
limited number of properties are exported.
Additional properties may be exported by simply setting the
`EXPORT_PROPERTIES` property on a target that is exported.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
5a7113d8fb VS: Add target property VS_DEBUGGER_COMMAND
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1842
|
| |/
| |
| |
| | |
Fixes: #17819
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
1f4d7a07 Help: Add references and backticks in LINK_FLAGS prop_tgt
48f7e2d3 Unhardcode the CMAKE_CONFIGURATION_TYPES values
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1345
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes duplicated code for per-config variable initialization by
providing a `cmake_initialize_per_config_variable(<PREFIX> <DOCSTRING>)`
function.
This function initializes a `<PREFIX>` cache variable from `<PREFIX>_INIT`
and unless the `CMAKE_NOT_USING_CONFIG_FLAGS` variable is defined, does
the same with `<PREFIX>_<CONFIG>` from `<PREFIX>_<CONFIG>_INIT` for every
`<CONFIG>` in `CMAKE_CONFIGURATION_TYPES` for multi-config generators or
`CMAKE_BUILD_TYPE` for single-config generators.
|
|/
|
|
| |
Fixes #17177.
|
|
|
|
|
|
|
|
|
|
| |
Add a `Fortran_COMPILER_LAUNCHER` target property like those added for C
and CXX by commit v3.4.0-rc1~450^2 (Add options to launch the compiler
through tools like ccache or distcc, 2015-06-04) and CUDA by commit
v3.10.0-rc1~531^2 (CUDA: Add option to run the compiler through launcher
tools, 2017-06-09).
Fixes: #17499
|
|\
| |
| |
| |
| |
| |
| |
| | |
00e13993 CUDA: Add CMAKE_CUDA_SEPARABLE_COMPILATION variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alexander Korsunsky <a.korsunsky@gmail.com>
Merge-request: !1495
|
| |
| |
| |
| |
| |
| |
| | |
Use its value to initialize the `CUDA_SEPARABLE_COMPILATION` target
property when targets are created.
Fixes: #17478
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The purpose of this new `IMPORTED_GLOBAL` target-property is to prolong
the lifetime and scope of `IMPORTED` targets in such a way as if they
had been created with the keyword `GLOBAL` in the first place.
* It can only be set to `TRUE`. That means, a local `IMPORTED` target
can be promoted to global scope but a global `IMPORTED` target cannot
be degraded to local scope!
* Setting it to `TRUE` only succeeds if done from within the same
directory in which the `IMPORTED` target was created in the first
place.
Fixes #17256.
|
|\
| |
| |
| |
| |
| |
| | |
e0587669 Help: Correct <LANG>_STANDARD help w.r.t. MSVC
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1401
|
| |
| |
| |
| | |
Fixes: #17380
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
22beb07f Help: Clarify documentation of NO_SYSTEM_FROM_IMPORTED
2de0e0fd Do not initialize NO_SYSTEM_FROM_IMPORTED on INTERFACE libraries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1386
|
| |/
| |
| |
| |
| |
| |
| | |
This property is meant to be set on the consumers of imported targets,
not the imported targets themselves.
Fixes: #17348
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
e95429fd Autogen: Docs: Extend SKIP_AUTOUIC documentation
814cddbe Autogen: Docs: Add examples for AUTORCC_OPTIONS and AUTOUIC_OPTIONS
1c196268 Autogen: Allow setting SKIP_AUTOUIC/GEN on .ui files not in the sources
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1366
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
a56d9ecf Help: Fix wrong property reference for an app bundle's Info.plist
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1362
|
| |/ |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
6bbc1e77 Autogen: Add release notes for (CMAKE_)AUTOMOC_COMPILER_PREDEFINES
75c98b5e Autogen: Doc: Add documentation for (CMAKE_)AUTOMOC_COMPILER_PREDEFINES
1d7f099d Autogen: Add (CMAKE_)AUTOMOC_COMPILER_PREDEFINES
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1328
|
| |
| |
| |
| |
| |
| | |
Also adds the documentation for CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND.
Closes #17275
|
|\ \
| |/
|/|
| |
| |
| |
| | |
fe37b994 CUDA: Add support for requesting C++98 under CUDA 9
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1315
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Starting in CUDA 9 the default compilation mode is C++14, and you need
to explicitly enable C++98/03 mode.
While at it, document `14` among the values for `CUDA_STANDARD`. This
was accidentally left out of commit v3.9.0-rc1~118^2 (CUDA: Add support
for the C++14 standard flag, 2017-05-11).
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Create a `<LANG>_CPPCHECK` target property (initialized by a
`CMAKE_<LANG>_CPPCHECK` variable) to specify a `cppcheck` command line
to be run along with the compiler.
|
| |
|
| |
|