vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
33 lines
1.4 KiB
ReStructuredText
33 lines
1.4 KiB
ReStructuredText
|
|
====================
|
|
Libc++ ABI stability
|
|
====================
|
|
|
|
Libc++ aims to preserve a stable ABI to avoid subtle bugs when code built under the old ABI
|
|
is linked with code built under the new ABI. At the same time, libc++ wants to make
|
|
ABI-breaking improvements and bugfixes in scenarios where the user doesn't mind ABI breaks.
|
|
|
|
To support both cases, libc++ allows specifying an ABI version at
|
|
build time. The version is defined with CMake option ``LIBCXX_ABI_VERSION``.
|
|
Currently supported values are ``1`` (the stable default)
|
|
and ``2`` (the unstable "next" version). At some point "ABI version 2" will be
|
|
frozen and new ABI-breaking changes will start being applied to version ``3``;
|
|
but this has not happened yet.
|
|
|
|
To always use the most cutting-edge, most unstable ABI (which is currently ``2``
|
|
but at some point will become ``3``), set the CMake option ``LIBCXX_ABI_UNSTABLE``.
|
|
|
|
Internally, each ABI-changing feature is placed under its own C++ macro,
|
|
``_LIBCPP_ABI_XXX``. These macros' definitions are controlled by the C++ macro
|
|
``_LIBCPP_ABI_VERSION``, which is controlled by the ``LIBCXX_ABI_VERSION`` set
|
|
at build time. Libc++ does not intend users to interact with these C++ macros
|
|
directly.
|
|
|
|
-----------------
|
|
MSVC environments
|
|
-----------------
|
|
|
|
The exception to this is MSVC environments. Libc++ does not currently have users
|
|
that require a stable ABI in MSVC environments, so MSVC-only changes may be
|
|
applied unconditionally.
|