[libcxx-commits] [PATCH] D111356: [runtimes] Use the new "runtimes" build by default and deprecate other builds

[Loïc Yhuel via Phabricator via libcxx-commits]

loic.yhuel added a comment.

Would several separate runtime builds with each time one project in `LLVM_ENABLE_RUNTIMES` work, to replace standalone builds ?

For custom embedded toolchains, there is sometime the need to do things in a specific order for bootstrapping :

- cmake on libcxx
- install libcxx headers
- cmake, build and install libunwind
- cmake and build libcxxabi
- build libcxx

IIRC, even with `CMAKE_TRY_COMPILE_TARGET_TYPE=STATIC_LIBRARY`, there is still the need to install certain headers for the cmake compile tests to work.

Sometimes there are also :

- custom `CXXFLAGS`/`LDFLAGS` for one project
- custom install steps (symlinks, linker scripts)

They could be needed for example to generate a gcc-like runtime on a Linux target for use by both clang and gcc : importing `__gcc_personality_v0` in libunwind to allow it to replace `libgcc_s.so.1` for glibc, `libgcc_eh.a` and `libgcc_s.so` linker scripts, ...


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D111356/new/

https://reviews.llvm.org/D111356