Florent Castelli a498d459a3 bindexplib: Export the same symbols on every host
WINDOWS_EXPORT_ALL_SYMBOLS reads object files with two backends: on
Windows hosts CMake walks the COFF symbol table itself, elsewhere (and
for LLVM bitcode) it parses `nm` output.  Only the walker applied the
rules the MSVC ABI needs, so a DLL cross-compiled from Linux or macOS
exported a different set of symbols than the same sources built on
Windows.

Move every rule that depends only on the symbol name into one place
used by both backends, and teach the nm backend the rest: skip
deleting destructors (`??_G`, `??_E`), export vftables (`??_7`) as code
except on ARM64EC where they are DATA, ignore common symbols, and strip
i386 decorations.  The machine type these need is read from the COFF
file header, once per object file.

The expected output of the nm symbol-type test changes accordingly.
Add a test running `cmake -E __create_def` over checked-in objects for
x86_64, i386 and ARM64EC against expected .def files, so one
expectation pins both backends.

Fixes: #28103
2026-09-30 02:45:08 +02:00
2026-09-23 13:44:30 -04:00
2026-09-20 11:43:10 +02:00
2026-09-07 09:18:35 -04:00
…
2026-01-01 00:06:14 -05:00

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`_. The `CMake Community Wiki`_ also
references useful guides and recipes.

.. _`CMake Home Page`: https://cmake.org
.. _`CMake Documentation Page`: https://cmake.org/documentation
.. _`CMake Community Wiki`: https://gitlab.kitware.com/cmake/community/-/wikis/home

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

.. _`Kitware`: https://www.kitware.com/cmake

License
=======

CMake is distributed under the OSI-approved BSD 3-clause License.
See `LICENSE.rst`_ for details.

.. _`LICENSE.rst`: LICENSE.rst

Building CMake
==============

Supported Platforms
-------------------

* Microsoft Windows
* Apple macOS
* Linux
* FreeBSD
* OpenBSD
* Solaris
* AIX

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.
Please post to the `CMake Discourse Forum`_ to ask if others have
had experience with the platform.

.. _`CMake Discourse Forum`: https://discourse.cmake.org

Building CMake with CMake
-------------------------

You can build CMake as any other project with a CMake-based build system:
run an already-installed CMake on this source tree with your preferred
generator and options.  Then build it and install it.

To build the documentation, install `Sphinx`_ and configure CMake with
``-DSPHINX_HTML=ON`` and/or ``-DSPHINX_MAN=ON`` to enable the "html" or
"man" builder.  Add ``-DSPHINX_EXECUTABLE=/path/to/sphinx-build`` if the
tool is not found automatically.  See the `CMake Documentation Guide`_ for
details.

To run the test suite, run ``ctest`` in the CMake build directory after
building.  See the `CMake Testing Guide`_ for details.

.. _`Sphinx`: https://sphinx-doc.org
.. _`CMake Documentation Guide`: Help/dev/documentation.rst
.. _`CMake Testing Guide`: Help/dev/testing.rst

Building CMake from Scratch
---------------------------

UNIX/Mac OSX/MinGW/MSYS/Cygwin
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You need to have a C++ compiler (supporting C++11) 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.  Once this has finished successfully,
run ``make`` and ``make install``.

For example, if you simply want to build and install CMake from source,
you can build directly in the source tree::

  $ ./bootstrap && make && sudo make install

Or, if you plan to develop CMake or otherwise run the test suite, create
a separate build tree::

  $ mkdir build && cd build
  $ ../bootstrap && make

By default the ``bootstrap`` script configures CMake to build with vendored
dependencies.  However, CMake does not vendor OpenSSL.  To bootstrap in a
minimal environment, disable use of OpenSSL::

  $ ./bootstrap -- -DCMAKE_USE_OPENSSL=OFF

Windows
^^^^^^^

There are two ways for building CMake under Windows:

1. Compile with MSVC from VS 2015 or later.
   You need to download and install a binary release of CMake.  You can get
   these releases from the `CMake Download Page`_.  Then proceed with the
   instructions above for `Building CMake with CMake`_.

2. Bootstrap with MinGW under MSYS2.
   Download and install `MSYS2`_.  Then install the required build tools::

     $ pacman -S --needed git base-devel mingw-w64-x86_64-gcc

   and bootstrap as above.

.. _`CMake Download Page`: https://cmake.org/download
.. _`MSYS2`: https://www.msys2.org/

Reporting Bugs
==============

If you have found a bug:

1. If you have a patch, please read the `CONTRIBUTING.rst`_ document.

2. Otherwise, please post to the `CMake Discourse Forum`_ 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`_.

.. _`CMake Issue Tracker`: https://gitlab.kitware.com/cmake/cmake/-/issues

Contributing
============

See `CONTRIBUTING.rst`_ for instructions to contribute.

.. _`CONTRIBUTING.rst`: CONTRIBUTING.rst
S
Description
No description provided
Readme
256 MiB
0 Stars 1 Watchers 0 Forks
Languages
C 39.4%
C++ 30%
CMake 27.7%
Roff 0.6%
Shell 0.5%
Other 1.2%