Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • release
  • v3.18.2
  • v3.18.1
  • v3.17.4
  • v3.18.0
  • v3.18.0-rc4
  • v3.18.0-rc3
  • v3.18.0-rc2
  • v3.18.0-rc1
  • v3.16.8
  • v3.17.3
  • v3.16.7
  • v3.17.2
  • v3.16.6
  • v3.17.1
  • v3.17.0
  • v3.17.0-rc3
  • v3.16.5
  • v3.17.0-rc2
  • v3.17.0-rc1
  • v3.16.4
22 results
Compare
Forked from CMake / CMake
33930 commits behind the upstream repository.
Brad King's avatar
VS: Fix GenerateDebugInformation values for v140 and v141 toolsets
Brad King authored 
When VS 2015 was first released, its new v140 toolset came with a
`link.xml` file that changed the `GenerateDebugInformation` boolean
(`false` and `true`) value from earlier toolsets to an enumeration
consisting of the possible values `No`, `Debug`, and `DebugFastLink`.

We first adapted to this in commit v3.4.2~2^2 (VS: Fix VS 2015 .vcxproj
file value for GenerateDebugInformation, 2016-01-08), but that broke
older toolsets that still expected the boolean.  Then commit
v3.6.0-rc1~295^2~1 (VS: Fix VS 2015 .vcxproj debug setting for older
toolsets, 2016-02-24) added a hack to fix up the value based on the
toolset in use.  Several follow-up commits fixed this for more older
toolsets because our flag table was at the time based on the generator
in use rather than the toolset in use.

Since commit v3.8.0-rc1~396^2 (VS: Choose flag map based on the toolset
name, 2016-10-17) we use a flag table based on the toolset, so the fixup
hack should not be needed.  We had to keep it around only due to our
default value for GenerateDebugInformation (`false` or `No`) still being
based on the generator instead of the toolset.

A VS 2015 update was released that changed the v140 toolset `link.xml`
file back to using `false` and `true` for the `GenerateDebugInformation`
enumeration variants previously known as `No` and `Debug`.  In order to
know which pair to use, we need to parse the `link.xml` file for the
current toolset.

Switch back to using `false` and `true` unconditionally in our
`GenerateDebugInformation` flag table entries and default value.  With
that plus the toolset-based flag table, we now get incorrect values for
`GenerateDebugInformation` only when using a v140 toolset from an older
VS 2015 installation.  Detect this case by parsing `link.xml` and add
special logic to convert `false` and `true` to `No` and `Debug` to
satisfy the older toolset specification.

Inspired-by: default avatarIan Hojnicki <nullref@live.com>
Fixes: #17020
ae44496e
History
Brad King's avatar ae44496e
History
Name Last commit Last update
Auxiliary
Help
Licenses
Modules
Packaging
Source
Templates
Tests
Utilities
.clang-format
.clang-tidy
.gitattributes
.gitignore
.hooks-config
CMakeCPack.cmake
CMakeCPackOptions.cmake.in
CMakeGraphVizOptions.cmake
CMakeLists.txt
CMakeLogo.gif
CONTRIBUTING.rst
CTestConfig.cmake
CTestCustom.cmake.in
CompileFlags.cmake
Copyright.txt
DartConfig.cmake
README.rst
bootstrap
cmake_uninstall.cmake.in
configure
doxygen.config
README.rst

CMake

Introduction

CMake is a cross-platform, open-source build system generator. For full documentation visit the CMake Home Page and the CMake Documentation Page.

CMake is maintained and supported by Kitware and developed in collaboration with a productive community of contributors.

License

CMake is distributed under the OSI-approved BSD 3-clause License. See Copyright.txt for details.

Building CMake

Supported Platforms

  • Microsoft Windows
  • Apple macOS
  • Linux
  • FreeBSD
  • OpenBSD
  • Solaris
  • HP-UX

Other UNIX-like operating systems may work too out of the box, if not it should not be a major problem to port CMake to this platform. Subscribe and post to the CMake Users List to ask if others have had experience with the platform.

Building CMake from Scratch

UNIX/Mac OSX/MinGW/MSYS/Cygwin

You need to have a compiler and a make installed. Run the bootstrap script you find in the source directory of CMake. You can use the --help option to see the supported options. You may use the --prefix=<install_prefix> option to specify a custom installation directory for CMake. You can run the bootstrap script from within the CMake source directory or any other build directory of your choice. Once this has finished successfully, run make and make install. In summary:

$ ./bootstrap && make && make install

Windows

You need to download and install a binary release of CMake in order to build CMake. You can get these releases from the CMake Download Page . Then proceed with the instructions below.

Building CMake with CMake

You can build CMake as any other project with a CMake-based build system: run the installed CMake on the sources of this CMake with your preferred options and generators. Then build it and install it. For instructions how to do this, see documentation on Running CMake.

Reporting Bugs

If you have found a bug:

  1. If you have a patch, please read the CONTRIBUTING.rst document.
  2. Otherwise, please join the CMake Users List and ask about the expected and observed behaviors to determine if it is really a bug.
  3. Finally, if the issue is not resolved by the above steps, open an entry in the CMake Issue Tracker.

Contributing

See CONTRIBUTING.rst for instructions to contribute.