From e87504429a264f4e5b5f94cc0997b4d1abd4dd8d Mon Sep 17 00:00:00 2001 From: Antonin Godard Date: Mon, 17 Feb 2025 15:50:22 +0100 Subject: [PATCH] migration-5.2: fix references to BB_CURRENT_MC Now part of the documentation. Reviewed-by: Quentin Schulz (From yocto-docs rev: 2a50504bd5c211bfae26db64190863fdf53fc3c9) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie --- documentation/migration-guides/migration-5.2.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst index de2ea773e5..75bc4dbc6f 100644 --- a/documentation/migration-guides/migration-5.2.rst +++ b/documentation/migration-guides/migration-5.2.rst @@ -97,12 +97,12 @@ systemd changes Multiconfig changes ~~~~~~~~~~~~~~~~~~~ -The value of ``BB_CURRENT_MC`` was changed from ``default`` to an empty string +The value of :term:`BB_CURRENT_MC` was changed from ``default`` to an empty string for the default multiconfig configuration to avoid needing to map the values within BitBake. This was already not happening in some cases so this fixes some obscure bugs. -Any logic based on ``BB_CURRENT_MC`` equalling to ``default`` by default should +Any logic based on :term:`BB_CURRENT_MC` equalling to ``default`` by default should be changed to be equal to an empty string. Virtual toolchain provider changes