[Buildroot] [PATCH RFC 1/1] Config.in: remove experimental status of per-package SDK and target

* [Buildroot] [PATCH RFC 1/1] Config.in: remove experimental status of per-package SDK and target
@ 2026-01-02 22:20 Bernd Kuhls
  2026-01-02 22:25 ` Thomas Petazzoni via buildroot
  0 siblings, 1 reply; 2+ messages in thread
From: Bernd Kuhls @ 2026-01-02 22:20 UTC (permalink / raw)
  To: buildroot

The last buildroot commit mentioning "per-pack" dates back to 2024:

$ LC_ALL=C git log --graph --pretty=format:'%h - %d %s (%cr) <%an>' --abbrev-commit -- | grep per-pack | head -n 1
* aa3ba97554 -  package/mender-grubenv: Fix per-package building (1 year, 3 months ago) <Adam Duskett>

so it should be safe to say that enabling BR2_PER_PACKAGE_DIRECTORIES
is not considered experimental anymore.

Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
 Config.in                     |  5 +----
 docs/manual/common-usage.adoc | 10 +++-------
 2 files changed, 4 insertions(+), 11 deletions(-)

diff --git a/Config.in b/Config.in
index d730f2034b..477db11f1c 100644
--- a/Config.in
+++ b/Config.in
@@ -788,7 +788,7 @@ config BR2_REPRODUCIBLE
 	  packages behave properly to ensure reproducibility.
 
 config BR2_PER_PACKAGE_DIRECTORIES
-	bool "Use per-package directories (experimental)"
+	bool "Use per-package directories"
 	help
 	  This option will change the build process of Buildroot
 	  package to use per-package target and host directories.
@@ -802,9 +802,6 @@ config BR2_PER_PACKAGE_DIRECTORIES
 
 	    - Enable top-level parallel build.
 
-	  This is labeled as an experimental feature, as not all
-	  packages behave properly with per-package directories.
-
 endmenu
 
 config BR2_TIME_BITS_64
diff --git a/docs/manual/common-usage.adoc b/docs/manual/common-usage.adoc
index 7437a7c3c0..dc8eddc4e2 100644
--- a/docs/manual/common-usage.adoc
+++ b/docs/manual/common-usage.adoc
@@ -402,9 +402,6 @@ utils/size-stats-compare -h
 === Top-level parallel build
 
 .Note
-This section deals with a very experimental feature, which is known to
-break even in some non-unusual situations. Use at your own risk.
-
 Buildroot has always been capable of using parallel build on a per
 package basis: each package is built by Buildroot using +make -jN+ (or
 the equivalent invocation for non-make-based build systems). The level
@@ -414,10 +411,9 @@ adjusted using the +BR2_JLEVEL+ configuration option.
 Until 2020.02, Buildroot was however building packages in a serial
 fashion: each package was built one after the other, without
 parallelization of the build between packages. As of 2020.02,
-Buildroot has experimental support for *top-level parallel build*,
-which allows some signicant build time savings by building packages
-that have no dependency relationship in parallel. This feature is
-however marked as experimental and is known not to work in some cases.
+Buildroot added support for *top-level parallel build*, which allows
+some signicant build time savings by building packages that have no
+dependency relationship in parallel.
 
 In order to use top-level parallel build, one must:
 
-- 
2.47.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

^ permalink raw reply related	[flat|nested] 2+ messages in thread