diff --git a/docs/manual/customize-directory-structure.txt b/docs/manual/customize-directory-structure.txt index 2ba9d28e25..ce2b0d7596 100644 --- a/docs/manual/customize-directory-structure.txt +++ b/docs/manual/customize-directory-structure.txt @@ -40,13 +40,12 @@ it using +BR2_EXTERNAL+. Both options are valid, the choice is up to you. | +-- / | +-- Config.in (if not using BR2_EXTERNAL) | +-- .mk (if not using BR2_EXTERNAL) -| +-- / -| +-- package1/ -| | +-- Config.in -| | +-- package1.mk -| +-- package2/ -| +-- Config.in -| +-- package2.mk +| +-- package1/ +| | +-- Config.in +| | +-- package1.mk +| +-- package2/ +| +-- Config.in +| +-- package2.mk | +-- Config.in (if using BR2_EXTERNAL) +-- external.mk (if using BR2_EXTERNAL) diff --git a/docs/manual/customize-outside-br.txt b/docs/manual/customize-outside-br.txt index 5fe7b60052..110984308f 100644 --- a/docs/manual/customize-outside-br.txt +++ b/docs/manual/customize-outside-br.txt @@ -81,19 +81,21 @@ The main usage of this is to store package recipes. The recommended looks like: + ------ -source "$BR2_EXTERNAL/package//package1/Config.in" -source "$BR2_EXTERNAL/package//package2/Config.in" +source "$BR2_EXTERNAL/package/package1/Config.in" +source "$BR2_EXTERNAL/package/package2/Config.in" ------ + Then, have a +$(BR2_EXTERNAL)/external.mk+ file that looks like: + ------ -include $(sort $(wildcard $(BR2_EXTERNAL)/package/*/*/*.mk)) +include $(sort $(wildcard $(BR2_EXTERNAL)/package/*/*.mk)) ------ + -And then in +$(BR2_EXTERNAL)/package//package1+ and - +$(BR2_EXTERNAL)/package//package2+ create normal Buildroot +And then in +$(BR2_EXTERNAL)/package/package1+ and + +$(BR2_EXTERNAL)/package/package2+ create normal Buildroot package recipes, as explained in xref:adding-packages[]. + If you prefer, you can also group the packages in subdirectories + called and adapt the above paths accordingly. * One can store Buildroot defconfigs in the +configs+ subdirectory of +$(BR2_EXTERNAL)+. Buildroot will automatically show them in the