2017-03-28 23:21:43 +08:00
|
|
|
.. _BuildingLibunwind:
|
|
|
|
|
|
|
|
==================
|
|
|
|
Building libunwind
|
|
|
|
==================
|
|
|
|
|
|
|
|
.. contents::
|
|
|
|
:local:
|
|
|
|
|
|
|
|
.. _build instructions:
|
|
|
|
|
|
|
|
Getting Started
|
|
|
|
===============
|
|
|
|
|
|
|
|
On Mac OS, the easiest way to get this library is to link with -lSystem.
|
|
|
|
However if you want to build tip-of-trunk from here (getting the bleeding
|
|
|
|
edge), read on.
|
|
|
|
|
|
|
|
The basic steps needed to build libc++ are:
|
|
|
|
|
2019-01-30 00:37:27 +08:00
|
|
|
#. Checkout LLVM, libunwind, and related projects:
|
2017-03-28 23:21:43 +08:00
|
|
|
|
|
|
|
* ``cd where-you-want-llvm-to-live``
|
2019-01-30 00:37:27 +08:00
|
|
|
* ``git clone https://github.com/llvm/llvm-project.git``
|
2017-03-28 23:21:43 +08:00
|
|
|
|
|
|
|
#. Configure and build libunwind:
|
|
|
|
|
|
|
|
CMake is the only supported configuration system.
|
|
|
|
|
|
|
|
Clang is the preferred compiler when building and using libunwind.
|
|
|
|
|
|
|
|
* ``cd where you want to build llvm``
|
|
|
|
* ``mkdir build``
|
|
|
|
* ``cd build``
|
2022-02-10 01:08:44 +08:00
|
|
|
* ``cmake -G <generator> -DLLVM_ENABLE_RUNTIMES=libunwind [options] <llvm-monorepo>/runtimes``
|
2017-03-28 23:21:43 +08:00
|
|
|
|
|
|
|
For more information about configuring libunwind see :ref:`CMake Options`.
|
|
|
|
|
|
|
|
* ``make unwind`` --- will build libunwind.
|
|
|
|
* ``make check-unwind`` --- will run the test suite.
|
|
|
|
|
|
|
|
Shared and static libraries for libunwind should now be present in llvm/build/lib.
|
|
|
|
|
|
|
|
#. **Optional**: Install libunwind
|
|
|
|
|
|
|
|
If your system already provides an unwinder, it is important to be careful
|
|
|
|
not to replace it. Remember Use the CMake option ``CMAKE_INSTALL_PREFIX`` to
|
|
|
|
select a safe place to install libunwind.
|
|
|
|
|
|
|
|
* ``make install-unwind`` --- Will install the libraries and the headers
|
|
|
|
|
|
|
|
|
|
|
|
It is sometimes beneficial to build outside of the LLVM tree. An out-of-tree
|
|
|
|
build would look like this:
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
$ cd where-you-want-libunwind-to-live
|
|
|
|
$ # Check out llvm, and libunwind
|
2020-03-23 05:42:03 +08:00
|
|
|
$ ``svn co https://llvm.org/svn/llvm-project/llvm/trunk llvm``
|
|
|
|
$ ``svn co https://llvm.org/svn/llvm-project/libunwind/trunk libunwind``
|
2017-03-28 23:21:43 +08:00
|
|
|
$ cd where-you-want-to-build
|
|
|
|
$ mkdir build && cd build
|
|
|
|
$ export CC=clang CXX=clang++
|
|
|
|
$ cmake -DLLVM_PATH=path/to/llvm \
|
|
|
|
path/to/libunwind
|
|
|
|
$ make
|
|
|
|
|
|
|
|
|
|
|
|
.. _CMake Options:
|
|
|
|
|
|
|
|
CMake Options
|
|
|
|
=============
|
|
|
|
|
|
|
|
Here are some of the CMake variables that are used often, along with a
|
|
|
|
brief explanation and LLVM-specific notes. For full documentation, check the
|
|
|
|
CMake docs or execute ``cmake --help-variable VARIABLE_NAME``.
|
|
|
|
|
|
|
|
**CMAKE_BUILD_TYPE**:STRING
|
|
|
|
Sets the build type for ``make`` based generators. Possible values are
|
|
|
|
Release, Debug, RelWithDebInfo and MinSizeRel. On systems like Visual Studio
|
|
|
|
the user sets the build type with the IDE settings.
|
|
|
|
|
|
|
|
**CMAKE_INSTALL_PREFIX**:PATH
|
|
|
|
Path where LLVM will be installed if "make install" is invoked or the
|
|
|
|
"INSTALL" target is built.
|
|
|
|
|
|
|
|
**CMAKE_CXX_COMPILER**:STRING
|
|
|
|
The C++ compiler to use when building and testing libunwind.
|
|
|
|
|
|
|
|
|
|
|
|
.. _libunwind-specific options:
|
|
|
|
|
|
|
|
libunwind specific options
|
|
|
|
--------------------------
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_ASSERTIONS:BOOL
|
|
|
|
|
|
|
|
**Default**: ``ON``
|
|
|
|
|
|
|
|
Toggle assertions independent of the build mode.
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_PEDANTIC:BOOL
|
|
|
|
|
|
|
|
**Default**: ``ON``
|
|
|
|
|
|
|
|
Compile with -Wpedantic.
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_WERROR:BOOL
|
|
|
|
|
|
|
|
**Default**: ``ON``
|
|
|
|
|
|
|
|
Compile with -Werror
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_SHARED:BOOL
|
|
|
|
|
|
|
|
**Default**: ``ON``
|
|
|
|
|
|
|
|
Build libunwind as a shared library.
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_STATIC:BOOL
|
|
|
|
|
|
|
|
**Default**: ``ON``
|
|
|
|
|
|
|
|
Build libunwind as a static archive.
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_CROSS_UNWINDING:BOOL
|
|
|
|
|
|
|
|
**Default**: ``OFF``
|
|
|
|
|
|
|
|
Enable cross-platform unwinding support.
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_ARM_WMMX:BOOL
|
|
|
|
|
|
|
|
**Default**: ``OFF``
|
|
|
|
|
|
|
|
Enable unwinding support for ARM WMMX registers.
|
|
|
|
|
|
|
|
.. option:: LIBUNWIND_ENABLE_THREADS:BOOL
|
|
|
|
|
|
|
|
**Default**: ``ON``
|
|
|
|
|
|
|
|
Build libunwind with threading support.
|
|
|
|
|
Prepare Compiler-RT for GnuInstallDirs, matching libcxx, document all
This is a second attempt at D101497, which landed as
9a9bc76c0eb72f0f2732c729a460abbd5239c2e3 but had to be reverted in
8cf7ddbdd4e5af966a369e170c73250f2e3920e7.
This issue was that in the case that `COMPILER_RT_INSTALL_PATH` is
empty, expressions like "${COMPILER_RT_INSTALL_PATH}/bin" evaluated to
"/bin" not "bin" as intended and as was originally.
One solution is to make `COMPILER_RT_INSTALL_PATH` always non-empty,
defaulting it to `CMAKE_INSTALL_PREFIX`. D99636 adopted that approach.
But, I think it is more ergonomic to allow those project-specific paths
to be relative the global ones. Also, making install paths absolute by
default inhibits the proper behavior of functions like
`GNUInstallDirs_get_absolute_install_dir` which make relative install
paths absolute in a more complicated way.
Given all this, I will define a function like the one asked for in
https://gitlab.kitware.com/cmake/cmake/-/issues/19568 (and needed for a
similar use-case).
---
Original message:
Instead of using `COMPILER_RT_INSTALL_PATH` through the CMake for
complier-rt, just use it to define variables for the subdirs which
themselves are used.
This preserves compatibility, but later on we might consider getting rid
of `COMPILER_RT_INSTALL_PATH` and just changing the defaults for the
subdir variables directly.
---
There was a seaming bug where the (non-Apple) per-target libdir was
`${target}` not `lib/${target}`. I suspect that has to do with the docs
on `COMPILER_RT_INSTALL_PATH` saying was the library dir when that's no
longer true, so I just went ahead and fixed it, allowing me to define
fewer and more sensible variables.
That last part should be the only behavior changes; everything else
should be a pure refactoring.
---
I added some documentation of these variables too. In particular, I
wanted to highlight the gotcha where `-DSomeCachePath=...` without the
`:PATH` will lead CMake to make the path absolute. See [1] for
discussion of the problem, and [2] for the brief official documentation
they added as a result.
[1]: https://cmake.org/pipermail/cmake/2015-March/060204.html
[2]: https://cmake.org/cmake/help/latest/manual/cmake.1.html#options
In 38b2dec37ee735d5409148e71ecba278caf0f969 the problem was somewhat
misidentified and so `:STRING` was used, but `:PATH` is better as it
sets the correct type from the get-go.
---
D99484 is the main thrust of the `GnuInstallDirs` work. Once this lands,
it should be feasible to follow both of these up with a simple patch for
compiler-rt analogous to the one for libcxx.
Reviewed By: phosek, #libc_abi, #libunwind
Differential Revision: https://reviews.llvm.org/D105765
2021-04-29 06:36:47 +08:00
|
|
|
.. option:: LIBUNWIND_INSTALL_LIBRARY_DIR:PATH
|
|
|
|
|
2022-08-19 10:44:46 +08:00
|
|
|
**Default**: ``lib${LIBUNWIND_LIBDIR_SUFFIX}``
|
Prepare Compiler-RT for GnuInstallDirs, matching libcxx, document all
This is a second attempt at D101497, which landed as
9a9bc76c0eb72f0f2732c729a460abbd5239c2e3 but had to be reverted in
8cf7ddbdd4e5af966a369e170c73250f2e3920e7.
This issue was that in the case that `COMPILER_RT_INSTALL_PATH` is
empty, expressions like "${COMPILER_RT_INSTALL_PATH}/bin" evaluated to
"/bin" not "bin" as intended and as was originally.
One solution is to make `COMPILER_RT_INSTALL_PATH` always non-empty,
defaulting it to `CMAKE_INSTALL_PREFIX`. D99636 adopted that approach.
But, I think it is more ergonomic to allow those project-specific paths
to be relative the global ones. Also, making install paths absolute by
default inhibits the proper behavior of functions like
`GNUInstallDirs_get_absolute_install_dir` which make relative install
paths absolute in a more complicated way.
Given all this, I will define a function like the one asked for in
https://gitlab.kitware.com/cmake/cmake/-/issues/19568 (and needed for a
similar use-case).
---
Original message:
Instead of using `COMPILER_RT_INSTALL_PATH` through the CMake for
complier-rt, just use it to define variables for the subdirs which
themselves are used.
This preserves compatibility, but later on we might consider getting rid
of `COMPILER_RT_INSTALL_PATH` and just changing the defaults for the
subdir variables directly.
---
There was a seaming bug where the (non-Apple) per-target libdir was
`${target}` not `lib/${target}`. I suspect that has to do with the docs
on `COMPILER_RT_INSTALL_PATH` saying was the library dir when that's no
longer true, so I just went ahead and fixed it, allowing me to define
fewer and more sensible variables.
That last part should be the only behavior changes; everything else
should be a pure refactoring.
---
I added some documentation of these variables too. In particular, I
wanted to highlight the gotcha where `-DSomeCachePath=...` without the
`:PATH` will lead CMake to make the path absolute. See [1] for
discussion of the problem, and [2] for the brief official documentation
they added as a result.
[1]: https://cmake.org/pipermail/cmake/2015-March/060204.html
[2]: https://cmake.org/cmake/help/latest/manual/cmake.1.html#options
In 38b2dec37ee735d5409148e71ecba278caf0f969 the problem was somewhat
misidentified and so `:STRING` was used, but `:PATH` is better as it
sets the correct type from the get-go.
---
D99484 is the main thrust of the `GnuInstallDirs` work. Once this lands,
it should be feasible to follow both of these up with a simple patch for
compiler-rt analogous to the one for libcxx.
Reviewed By: phosek, #libc_abi, #libunwind
Differential Revision: https://reviews.llvm.org/D105765
2021-04-29 06:36:47 +08:00
|
|
|
|
|
|
|
Path where built libunwind libraries should be installed. If a relative path,
|
|
|
|
relative to ``CMAKE_INSTALL_PREFIX``.
|