| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit 33c15ae2b9 (VS: Build custom commands concurrently when
possible, 2023-01-19, v3.26.0-rc1~56^2) we add `BuildInParallel` to
custom commands in `.vcxproj` files. However, this can break existing
projects that implicitly rely on serial execution of custom commands.
For example, custom commands in our FindCUDA module run MSVC (via nvcc)
with a common `vc*.pdb` file, and therefore cannot run in parallel.
Revert use of `BuildInParallel` while leaving most of the infrastructure
for it in place. It can be restored later with an option or policy.
Fixes: #24576
Issue: #18405
|
|
|
|
|
|
|
|
| |
The Ninja and Makefile generators honor `target_compile_options` and
friends for ASM_NASM `.asm` sources. Teach the VS generator to
honor them too for consistency.
Issue: #24289
|
|
|
|
|
|
|
|
| |
The Ninja and Makefile generators honor `target_compile_options` and
friends for ASM_MARMMASM `.asm` sources. Teach the VS generator to
honor them too for consistency.
Issue: #24289
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit 33c15ae2b9 (VS: Build custom commands concurrently when
possible, 2023-01-19) several tests have failed intermittently with the
VS generator. It seems that if the `BuildInParallel` setting is
attached to a generated input:
<CustomBuild Include="generated_input.txt">
<BuildInParallel Condition="...">true</BuildInParallel>
<Command Condition="...">copy geneated_input.txt output.txt</Command>
...
</CustomBuild>
then MSBuild does not wait for the input to be generated before running
the command.
This occurs when using `add_custom_command`'s `MAIN_DEPENDENCY`, so
avoid using `BuildInParallel` in that case.
Issue: #18405
|
|
|
|
|
|
| |
Enable the `BuildInParallel` setting in VS project files when supported.
Fixes: #18405
|
| |
|
|
|
|
|
|
|
|
| |
The Ninja and Makefile generators honor `target_compile_options`
and friends for MASM `.asm` sources. Teach the VS generator to
honor them too for consistency.
Fixes: #24289
|
|\ |
|
| |
| |
| |
| |
| | |
MSBuild enables debug information with MASM by default, but for us
that is not consistent with behavior on other generators.
|
| |
| |
| |
| |
| |
| | |
Improve parity with classic MSBuild projects.
Fixes: #23415
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Extend commit b325484928 (VS: Fix C language standard in target with C++
sources, 2020-09-28, v3.19.0-rc1~74^2) to account for users placing a
`-std:` flag in `CMAKE_C_FLAGS`.
|
| | |
|
| |
| |
| |
| |
| |
| | |
https://learn.microsoft.com/en-us/cpp/assembler/arm/arm-assembler-reference
Fixes: #23999
|
|/
|
|
|
|
| |
Generate `CLRSupport` for Visual Studio projects.
Fixes: #22054
|
|
|
|
|
|
|
|
|
|
| |
Set the `AppendTargetFrameworkToOutputPath` property to `false` only for
single target SDK-style projects. This prevents outputs from being
overwritten during the build. This revises commit 7671d71299 (VS: Fix
target output paths in SDK-style projects, 2022-09-23, v3.25.0-rc1~82^2).
Fixes: #24094
Issue: #23989
|
|\
| |
| |
| |
| |
| |
| | |
8d6f015d59 Drop Visual Studio 10 2010 generator
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7718
|
| |
| |
| |
| | |
This generator has been deprecated since CMake 3.22. Remove it.
|
|/
|
|
|
|
|
|
| |
Set the `AppendTargetFrameworkToOutputPath` property to `false` so that
MSBuild does not append anything extra to our standard target output
paths. This fixes the `INSTALL` target, among other things.
Fixes: #23989
|
|
|
|
|
|
| |
Extend the fix from commit a450cc9533 (VS: Set ResolveNugetPackages to
false for ALL_BUILD and ZERO_CHECK, 2021-12-15, v3.23.0-rc1~196^2~1) to
the `PACKAGE` target too.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
96bc59b1ca CUDA: Add Device LTO support for nvcc
1527d48cd0 CheckIPO: Refactor logic selecting test source files
4a552ab4ad remove unused variables
6eda92d037 remove unused variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7389
|
| |
| |
| |
| | |
Fixes #22200
|
| |
| |
| |
| | |
Fixes: #23772
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
feeb9ae4ba VS: Add support for (lib)fuzzer /fsanitize=fuzzer flag
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7471
|
| |/ |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Revert commit a334f1b906 (VS: Write ZERO_CHECK.proj for VS19 and above,
2021-12-24, v3.24.0-rc1~607^2) and a supporting change from
commit 7219988b00 (VS: Exclude ZERO_CHECK.proj from .sln for
include_external_msproject, 2022-07-15, v3.24.0-rc4~1^2).
The change was made to support `dotnet` tooling in addition to
`msbuild`. However, not having `ZERO_CHECK` in the `.sln` breaks common
interactive workflows. Revert the change for now. Later it can be
re-introduced behind some kind of option that enables `dotnet` support.
Fixes: #23726
Issue: #20227
|
| |/
|/|
| |
| |
| |
| | |
This prevents MSBuild from complaining with warning MSB8028.
Fixes #23043
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
07bc3b07ec gitlab-ci: test C++ modules using GCC
1b2270aa4e ci: add a Docker image to test out C++ modules with GCC
8c5a53096a Tests/RunCMake/CXXModules: add module-using examples
4151547e2f cmGlobalNinjaGenerator: use `cmModuleMapper` implementation
b43bdaff3c cmCxxModuleMapper: implement support for GCC's module map format
02d0f0e752 cmCxxModuleMapper: add source to handle module mapper contents
a046a45aad cmGlobalNinjaGenerator: add a TODO for header units
386465bf83 cmTarget: add support for C++ module fileset types
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7369
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
C++ modules have two variants which are of importance to CMake:
- `CXX_MODULES`: interface modules (those using `export module M;`,
`export module M:part;`, or `module M:internal_part;`)
- `CXX_MODULE_HEADER_UNITS`: importable header units
Creating C++ modules or partitions are *not* supported in any other
source listing. This is because the source files must be installed (so
their scope matters), but not part of usage requirements (what it means
for a module source to be injected into a consumer is not clear at this
moment). Due to the way `FILE_SET` works with scopes, they are a perfect
fit as long as `INTERFACE` is not allowed (which it is not).
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
e3983168da CUDA: MSVC pass all cuda gencode flags via AdditionalOptions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7359
|
| |/
| |
| |
| | |
Fixes #23491
|
|/ |
|
|
|
|
|
|
|
| |
Map `CMAKE_SYSTEM_VERSION` to the Android Target API Level for Visual
Studio projects.
Fixes: #22886
|
|\
| |
| |
| |
| |
| |
| | |
7a2496daad VS: Add support for SYSTEM include directories
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7238
|