| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
282d9f3168 MSVC: Document behavior when MSVC_RUNTIME_LIBRARY is not set
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3573
|
| |
| |
| |
| |
| | |
By default `CMAKE_MSVC_RUNTIME_LIBRARY` is not set. Document the
default runtime library selection in that case. We already test it.
|
| |\
| | |
| | |
| | | |
Merge-request: !3478
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !3466
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On AIX, plugins meant to be loaded into executables via `dlopen` must be
linked with access to a list of symbols exported from the executable in
order to use them (when not using runtime linking). The AIX linker
supports specifying this list as an "import file" passed on the command
line either via the `-bI:...` option or (with a leading `#! .` line) as
a normal input file like any other library file.
The linker import file plays the same role on AIX as import libraries do
on Windows. Teach CMake to enable its import library abstraction on AIX
for executables with the `ENABLE_EXPORTS` target property set. Teach
our internal `ExportImportList` script to optionally generate a leading
`#! .` line at the top of the generated export/import list. Update our
rule for linking an executable with exports to generate a public-facing
"import library" implemented as an AIX linker import file.
With this approach, our existing infrastructure for handling import
libraries on Windows will now work for AIX linker import files too:
* Plugins that link to their executable's symbols will be automatically
linked using the import file on the command line.
* The executable's import file will be (optionally) installed and
exported for use in linking externally-built plugins.
This will allow executables and their plugins to build even if we later
turn off runtime linking.
Issue: #19163
|
| | | |
| | | |
| | | |
| | | | |
Spell out the behavior on each platform in a bullet list.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
cd92f8f8bf VS: Add VS_DPI_AWARE target property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3418
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Enables setting the visual studio project property for Manifests,
controlling the DPI Aware setting.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
d29ed8a114 BUILD_RPATH/INSTALL_RPATH: Add generator expression support
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3481
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes: #19423
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | /
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
f57a53d43e Help: Document that CMAKE_FRAMEWORK initializes FRAMEWORK target prop
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3478
|
| |/ / / |
|
|\ \ \ \
| |_|/ /
|/| | /
| | |/
| |/|
| | |
| | |
| | | |
96c6bc2584 Help: Improve documentation of IMPORTED_LOCATION property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alex Turbov <i.zaufi@gmail.com>
Merge-request: !3466
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Mention the usage of a configuration specific
`IMPORTED_LOCATION_<CONFIG>` value even if the `<CONFIG>` is not the
same as the active configuration of the currently built project.
Co-Author: Brad King <brad.king@kitware.com>
|
| |
| |
| |
| |
| |
| |
| | |
- Rewrites and restructures the AUTOMOC target property documentation
- Remove the reference to the deprecated CMAKE_AUTOMOC_RELAXED_MODE
Fixes: #19167
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
Extend the `ADDITIONAL_CLEAN_FILES' target and directory property
documentation.
Fixes: #19341
|
|
|
|
| |
Copy wording from the release notes.
|
|
|
|
| |
Fixes: #19321
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
a59662bb5b Help: Add CheckIPOSupported link to INTERPROCEDURAL_OPTIMIZATION
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3333
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a9180ccf9a Tests: add a check for the Swift compiler
d745551fb6 Help: add some initial documentation for Swift support
9a182c9e5b Auxiliary: update vim syntax highlighting
e9b0063e8e Modules: add build rules for Swift Ninja support
b6412e3e38 Ninja: add placeholders to support Swift build
7d7f31161d Ninja: add support for Swift's output-file-map.json
d688c4c19d Swift: remove unnecessary unreleased Ninja infrastructure
0723582208 Swift: Detect compiler version
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3297
|
| |/ |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
93ee7dd044 Autogen: Update documentation for ADDITIONAL_CLEAN_FILES
4b4fd99f41 Autogen: Use ADDITIONAL_CLEAN_FILES target property for file cleaning
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3327
|
| |
| |
| |
| |
| | |
Update the AUTOGEN documentation for the use of `ADDITIONAL_CLEAN_FILES`
instead of `ADDITIONAL_MAKE_CLEAN_FILES`.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
2a9ff9703e MSVC: Add support for /JMC (Just My Code)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3121
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
Extend tests added by commit fb3370b6a1 (MSVC: Add abstraction for
runtime library selection, 2019-04-10) to cover an empty value for
the property. It should result in no specific setting.
Issue: #19108
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
fb3370b6a1 MSVC: Add abstraction for runtime library selection
f621e7fa5d VS: Fix Fortran runtime library flag map special case for '-' options
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Acked-by: Leonid Pospelov <pospelovlm@yandex.ru>
Merge-request: !3211
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replace our hard-coded defaults for `/MD` and `/MDd` with a first-class
abstraction to select the runtime library from an enumeration of logical
names. We've long hesitated to do this because the idea of "runtime
library selection" touches on related concepts on several platforms.
Avoid that scope creep by simply defining an abstraction that applies
only when targeting the MSVC ABI on Windows.
Removing the old default flags requires a policy because existing
projects may rely on string processing to edit them and choose a runtime
library under the old behavior. Add policy CMP0091 to provide
compatibility.
Fixes: #19108
|
|\ \
| |/
|/|
| |
| |
| |
| | |
d145d72e70 VS: add target property VS_PROJECT_IMPORT_<propspath>
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3143
|
| |
| |
| |
| | |
Fixes: #18998
|
| |
| |
| |
| |
| | |
This was added accidentally by commit 456e0fb64f (Help: Improve
documentation formating, 2019-04-01).
|
|/ |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
bf10f02441 Help: Fix minor inaccuracies of what BUILD_RPATH_USE_ORIGIN affects
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3020
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
917c035ada VS: support suppressing deployment of selected targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2991
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Add a `VS_NO_SOLUTION_DEPLOY` target property to explicitly specify for
each target whether to suppress VS solution deployment of the generated
target project.
Fixes: #18953
|
|/
|
|
|
|
|
|
|
| |
The original warning pre-dates support for install components.
There are now legitimate scenarios where an install(TARGETS)
command may list a target that is excluded from all, e.g.
hierarchical projects that will never install the component such a
target belongs to.
Fixes: #18938
|
|
|
|
| |
-- Also change variable name to CMAKE_GHS_NO_SOURCE_GROUP_FILE
|
|
|
|
|
|
|
| |
`CUDA_RESOLVE_DEVICE_SYMBOLS` can be used with shared, module, and
executable target types. This relaxation is to allow for better
interoperability with linkers that automatically do CUDA device symbol
resolution and have no way to disable it.
|
|\
| |
| |
| |
| |
| |
| | |
dc6888573d Pass EXCLUDE_FROM_ALL from directory to targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2816
|
| |
| |
| |
| |
| |
| | |
When a target is created it now inherits the EXCLUDE_FROM_ALL property
from its directory. This change makes it possible to include a target
in "all", even if its directory has been marked as EXCLUDE_FROM_ALL.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-- Check the property "ghs_integrity_app" on executables to set [INTEGRITY Application]
If the property is not set then check if an integrate file is one of the source files (.int file).
Dynamic Downloads that do not have an integrate file can use this property along with setting
the compiler flag "-dynamic".
-- Remove parsing for -dynamic flag; it is only used to print a comment
The MULTI GUI will show if it is a Monolith or Dynamic Download application
-- Use project references to specify which executables are part of the Integrity Application
Usually Implicit Dependency Analysis will ensure that executable targets
become part of the application. This does not work for Dynamic Download without integrate files.
Use `add_dependencies(dd vas)` to mark that the vas target is part of dd target.
-- Update file locations in the Integrate files.
|