Author: Martin Storsjö Date: 2022-08-15T14:27:47+03:00 New Revision: 7af201cba581930f990f70cb99bb91e7a046b307
URL: https://github.com/llvm/llvm-project/commit/7af201cba581930f990f70cb99bb91e7a046b307 DIFF: https://github.com/llvm/llvm-project/commit/7af201cba581930f990f70cb99bb91e7a046b307.diff LOG: [libcxx] [doc] Remove a leftover tentative release note This release note was added tentatively in https://reviews.llvm.org/D120982 / ebde6fc23bc0ee9d022fcd26b52bc82dfb7c8468. The issue was resolved differently in https://reviews.llvm.org/D125715 / bedf657d0f4c54ffe9ef4303382657a74296b544, but that commit forgot to remove the tentative release note. Added: Modified: libcxx/docs/ReleaseNotes.rst Removed: ################################################################################ diff --git a/libcxx/docs/ReleaseNotes.rst b/libcxx/docs/ReleaseNotes.rst index 6acde0db864bf..9fd114a05585d 100644 --- a/libcxx/docs/ReleaseNotes.rst +++ b/libcxx/docs/ReleaseNotes.rst @@ -239,11 +239,6 @@ Build System Changes use the ``CMAKE_CXX_COMPILER_TARGET``, ``CMAKE_SYSROOT`` and ``CMAKE_CXX_COMPILER_EXTERNAL_TOOLCHAIN`` variables provided by CMake. -- When building for Windows, vendors who want to avoid dll-exporting symbols from the static libc++abi - library should set ``LIBCXXABI_HERMETIC_STATIC_LIBRARY=ON`` when configuring CMake. The current - behavior, which tries to guess the correct dll-export semantics based on whether we're building - the libc++ shared library, will be removed in LLVM 16. - - Previously, the C++ ABI library headers would be installed inside ``<prefix>/include/c++/v1`` alongside the libc++ headers as part of building libc++. This is not the case anymore -- the ABI library is expected to install its headers where it wants them as part of its own build. _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
