GitLab

da79075c CTest: Generate Done.xml before calculating its hash
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3563

Fixes: #19489

8738e258 cmGlobalNinjaGenerator: Use gnu compatible paths with QCC
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3567

3bed969d cmMakefile: Modernize AddFunctionBlocker method to accept a std::unique_ptr
faacb90a cmELF: Modernize to use std::unique_ptr instead of new/delete
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3548

282d9f31 MSVC: Document behavior when MSVC_RUNTIME_LIBRARY is not set
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3573

c1fc6c80 VS: Place intermediate files in the "ASM List Location" next to objects
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3569

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.

6cc4ca31 Fix repeated word in FindVulkan.cmake
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3575

Merge-request: !3569

The `AssemblerListingLocation` setting in VS project files is meant for
intermediate files created during the build much like object files.
When the VS 7 generator was first under development, commit 49aebe6c
(new arch, 2002-09-04) placed both object files and the ASM list
location in the same directory.  Later commit f9aef0e4 (Generator now
creates a separate intermediate files directory for each target,
2005-07-27) moved the object files to a per-target directory but the
ASM list location was not moved with them.  Move it now.

Fixes: #19480

f19c189e Merge branch 'backport-swift-improvements' into swift-improvements
5803a8a2 Swift: support SONAME on ELFish targets
47e28cbe Swift: support multithreaded compilation
6814567e Swift: add rules for static linking
c8741e8f Swift: Add library search paths for dependencies
be0d4042 Support per-language library link flags
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3568

Merge-request: !3568

696d0f9c FindPython: ensure interpreter is founded when cross-compiling
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3564

Merge-request: !3564

Fixes: #19473

3fb3157d AIX: Do not enable runtime linking by default anymore
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3566

We should enable the soname to be setup for ELF shared libraries.
Failure to do so generates binaries with incorrect names which prevents
loading.

Query the number of logical CPUs available to enable parallel
compilation for Swift.

The Swift driver recently learnt how to generate static libraries using
the `-static` flag.  This enables us to generate proper static libraries
with dependency tracking with Swift as well.

When building Swift executables and libraries which import a module, an
implicit link will be added by the driver.  Because this links by name
rather than path, the library search path needs to be provided to
indicate where to find the library.  For all local dependencies, add the
library paths for the targets when linking.  This ensures that you can
link against local libraries without explicitly setting a library path.

Fixes: #19304

This changes the behaviour of the generators to use a per-language
library search path flag.  This is needed for multi-language projects
with different compilers (e.g. cl + gfortran).  Since the adjusted
variable has been part of the user settings, we control this based on a
policy.

Fixes: #19307

We've long created shared objects on AIX using the linker's `-G` option
(also offered by the XL front-end).  The `-G` option implies `-brtl` and
enables runtime linking.  This has been largely unnecessary because we
provide all dependencies on the link line and both XL and GNU compilers
offer builtin behavior to export symbols.  Since commit 0f150b69 (AIX:
Explicitly compute shared object exports for both XL and GNU,
2019-07-11) we compute exports explicitly and consistently.
Therefore runtime linking is no longer necessary for shared objects.

We've also long created executables on AIX using the linker's `-brtl`
option to enable runtime linking in case they load plugins at runtime.
Since commit 9f5c2040 (AIX: Explicitly compute executable exports for
both XL and GNU, 2019-07-12) and commit 2fa920c0 (AIX: Create import
library for executables with exports, 2019-07-16) we now provide the
linker enough information to fully resolve symbols in plugins up front.
Therefore runtime linking is no longer necessary for executables.

Drop use of `-G` for creating shared objects and use the XL `-qmkshrobj`
and GCC `-shared` options instead.  Both invoke the linker with the
`-bM:SRE -bnoentry` options to create a shared object without runtime
linking enabled.  Also drop use of `-brtl` for creating executables.

Issue: #19163

2fa920c0 AIX: Create import library for executables with exports
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3561

0518e675 CMake.qch: Don't include the version in the file name
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3558

Fixes: #19374

0ba5891e project: Keep leading `0` in PROJECT_VERSION components
5f846698 Tests: Factor out RunCMake.project helper macro into module
b1f387a7 Refactor: Use raw string literals instead of escaping
41b85968 Refactor: Use initializer lists instead of `push_back` series
45e85dd2 Refactor: Add some `const` to vars
90f91e4d Refactor: Replace a "magic" number w/ a named constant
638383c3 Refactor: Eliminate one-time-used variables
9b6a5329 Refactor: Eliminate `sep` from the loop
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3517

f2edccea find_package: Fix NO_MODULE under CMAKE_FIND_PACKAGE_PREFER_CONFIG
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3557