CMake merge requestshttps://gitlab.kitware.com/cmake/cmake/-/merge_requests2024-02-14T21:16:16-05:00https://gitlab.kitware.com/cmake/cmake/-/merge_requests/568CMP0069 (INTERPROCEDURAL_OPTIMIZATION behavior)2024-02-14T21:16:16-05:00Ruslan Baratovx@ruslo.devCMP0069 (INTERPROCEDURAL_OPTIMIZATION behavior)~~Patch created on top of https://gitlab.kitware.com/cmake/cmake/merge_requests/564. Waiting for it to be merged.~~ This patch is ready for testing.
Topic-rename: ipo-policy-CMP0069~~Patch created on top of https://gitlab.kitware.com/cmake/cmake/merge_requests/564. Waiting for it to be merged.~~ This patch is ready for testing.
Topic-rename: ipo-policy-CMP00693.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/879Sunpro std flags2023-05-31T14:11:21-04:00Daniel PfeiferSunpro std flags3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/739Deprecate Visual Studio 8 2005 generator2023-02-08T12:02:09-05:00Brad KingDeprecate Visual Studio 8 2005 generatorUpdate documentation to mark the generator deprecated. Add a warning at the end of generation plus an option to turn off the warning.Update documentation to mark the generator deprecated. Add a warning at the end of generation plus an option to turn off the warning.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/566CUDA: Add support to the Visual Studio generators2022-12-13T03:55:34-05:00Brad KingCUDA: Add support to the Visual Studio generatorsImplement support for the `CUDA` language in generators for Visual Studio 10 and above (Makefile and Ninja generators already support it). Use the CUDA Toolkit's VS integration features to give developers a first-class experience with g...Implement support for the `CUDA` language in generators for Visual Studio 10 and above (Makefile and Ninja generators already support it). Use the CUDA Toolkit's VS integration features to give developers a first-class experience with generated projects.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/428Added support NASM for Visual Studio generators2022-10-24T14:34:51-04:00Evgeny FimochkinAdded support NASM for Visual Studio generatorsI wrote a fix for bug :#16469:. Added descriptions nasm (xml like embedded for nasm) tools for Visual Studio and
I was testing it on VS 2013 and 2015.I wrote a fix for bug :#16469:. Added descriptions nasm (xml like embedded for nasm) tools for Visual Studio and
I was testing it on VS 2013 and 2015.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/430ninja: break unnecessary target dependencies2021-06-01T10:04:14-04:00Ben Boeckelninja: break unnecessary target dependenciesPreviously, given two libraries, X and Y where X depends on Y, all
object compilations of X would require the Y library to have been linked
before being compiled. This is not necessary and can instead be loosened
such that object comp...Previously, given two libraries, X and Y where X depends on Y, all
object compilations of X would require the Y library to have been linked
before being compiled. This is not necessary and can instead be loosened
such that object compilations of X only depend on the order-only
dependencies of Y to be completed. This is to ensure that generated
sources, headers, custom commands, etc. are completed before X starts to
compile its objects.
This should help build performance in projects with many libraries which
cause a deep library dependency chain. Previously, a library at the
bottom would not start compilation until after all other libraries
completed, but now only its link step needs to wait and its compilation
jobs can be run in parallel with other tasks.
Fixes #15555.
3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/669Include external msproject map config2021-04-08T09:32:12-04:00beebleInclude external msproject map configExtend Visual Studio sln generator to accept MAP_IMPORTED_CONFIG_*.
This allows 3rd party projects added via include_external_msproject, to compile preferred configuration despite different naming standard
Inspired by old mail: https:/...Extend Visual Studio sln generator to accept MAP_IMPORTED_CONFIG_*.
This allows 3rd party projects added via include_external_msproject, to compile preferred configuration despite different naming standard
Inspired by old mail: https://cmake.org/pipermail/cmake/2010-April/036388.html
--
Reopen of accidentally closed: Merge Request !6643.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/767UseSWIG: Fall back to empty PREFIX for unknown languages2020-12-02T11:15:51-05:00Brad KingUseSWIG: Fall back to empty PREFIX for unknown languagesTeach `SWIG_ADD_LIBRARY` to fall back to an empty library prefix for languages we don't explicitly define already.Teach `SWIG_ADD_LIBRARY` to fall back to an empty library prefix for languages we don't explicitly define already.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/712Extend support for OBJECT libraries2020-09-24T12:53:01-04:00Brad KingExtend support for OBJECT librariesLift some of our limitations on using object libraries:
* Allow them to be exported, imported, and installed.
* Allow use of the `$<TARGET_OBJECTS:...>` generator expression everywhere.Lift some of our limitations on using object libraries:
* Allow them to be exported, imported, and installed.
* Allow use of the `$<TARGET_OBJECTS:...>` generator expression everywhere.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/794PGI: Add Windows support2020-09-16T10:45:22-04:00Christian PfeifferPGI: Add Windows supportPGI compilers on Windows currently do not work. The -Mipa switch was removed in version 16.3 and PGI ships its own ar on Windows - and only there - that behaves differently to GNU binutils, i.e. ar -r does what ar qc does for binutils.PGI compilers on Windows currently do not work. The -Mipa switch was removed in version 16.3 and PGI ships its own ar on Windows - and only there - that behaves differently to GNU binutils, i.e. ar -r does what ar qc does for binutils.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/635Resolve "Add generator expressions for macOS bundle targets"2020-07-24T02:27:42-04:00Gregor JasnyResolve "Add generator expressions for macOS bundle targets"Closes #16733Closes #167333.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/784Add language standards to more compilers2020-07-17T06:31:06-04:00Chuck AtkinsAdd language standards to more compilers3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/516cmCPackDragNDropGenerator: Improving handling of temporary image format.2020-06-30T06:43:50-04:00Clinton StimpsoncmCPackDragNDropGenerator: Improving handling of temporary image format.Adjust which image format to create the initial dmg, and convert only
when necessary.
This eliminates random "hdiutil create -format UDRW" failures I'm seeing
which may be related to an anti-virus scanner.
"hdiutil create -format UDRW -...Adjust which image format to create the initial dmg, and convert only
when necessary.
This eliminates random "hdiutil create -format UDRW" failures I'm seeing
which may be related to an anti-virus scanner.
"hdiutil create -format UDRW -verbose" indicates a "resource is busy" issue
when unmounting an image.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/783Features: On SunPro link with language standard compiler flag2020-06-22T07:08:04-04:00Brad KingFeatures: On SunPro link with language standard compiler flagWhen C++ feature requirements or `CXX_STANDARD` cause us to compile on SunPro with the `-std=c++11` option, link with the option too. This is needed to make the compiler use the matching standard library.When C++ feature requirements or `CXX_STANDARD` cause us to compile on SunPro with the `-std=c++11` option, link with the option too. This is needed to make the compiler use the matching standard library.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/701Prepare to support per-config object library files2020-05-15T08:28:48-04:00Brad KingPrepare to support per-config object library filesDrop object libraries from GetConfigCommonSourceFiles. Call sites such as those in the VS global generator that are used only to reject per-config sources will now allow per-config object library objects. Teach the corresponding genera...Drop object libraries from GetConfigCommonSourceFiles. Call sites such as those in the VS global generator that are used only to reject per-config sources will now allow per-config object library objects. Teach the corresponding generators to deal with per-config object library files and not use `GetConfigCommonSourceFiles` to get them. Remaining call sites do not need object library files anyway.
This will later allow `$<TARGET_OBJECTS:...>` generator expressions to evaluate to values that vary by configuration (e.g. because each configuration has its own object files).3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/924Provide and use CM_FALLTHROUGH2020-04-25T17:02:18-04:00Daniel PfeiferProvide and use CM_FALLTHROUGH@brad.king, this should go into 3.9, as it fixes some warnings on GCC 7.1.@brad.king, this should go into 3.9, as it fixes some warnings on GCC 7.1.3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/509CMake Xcode Schemes2020-01-24T09:52:24-05:00Gregor JasnyCMake Xcode SchemesPR in favor of !415PR in favor of !4153.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/696VS: Add an environment variable for the Windows 10 kits directory2019-09-13T13:05:13-04:00Brad KingVS: Add an environment variable for the Windows 10 kits directoryDefine a `CMAKE_WINDOWS_KITS_10_DIR` environment variable to allow
users to tell CMake about a custom Windows 10 SDK directory. We
choose to make this an environment variable rather than a CMake
variable or cache entry because:
* Using...Define a `CMAKE_WINDOWS_KITS_10_DIR` environment variable to allow
users to tell CMake about a custom Windows 10 SDK directory. We
choose to make this an environment variable rather than a CMake
variable or cache entry because:
* Using a custom directory also requires custom external MSBuild
configuration. Therefore users are already configuring a
custom environment.
* The custom directory must be set consistently in all parts of
a build including nested projects. An environment variable
avoids requiring users to thread the setting into nested builds.
Fixes: #167433.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/692Add include-what-you-use mapping2019-07-09T11:37:18-04:00Daniel PfeiferAdd include-what-you-use mapping3.9.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/merge_requests/1019FindDoxygen: Create DOXYGEN_OUTPUT_DIRECTORY if it doesn't exist2019-05-09T08:22:38-04:00Robert DaileyFindDoxygen: Create DOXYGEN_OUTPUT_DIRECTORY if it doesn't existIf the doxygen output directory does not exist, create it prior to
running the doxygen commands.
Topic-rename: FindDoxygen-create-output-dir
If the doxygen output directory does not exist, create it prior to
running the doxygen commands.
Topic-rename: FindDoxygen-create-output-dir
3.9.0Brad KingBrad King