jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 06:06:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

manual/user guide/customization: change recommendation for package paths

Browse Source 
The Buildroot manual was recommending following paths for project-specific
packages:
    package/<company>/<boardname>/foo/
    $BR2_EXTERNAL/package/<boardname>/foo/

However, if a company has several boards, it is often the case that some
packages are common for different boards. Therefore, introducing a
<boardname> path component is not ideal.

This patch changes the recommendation to:
    package/<company>/foo/
    $BR2_EXTERNAL/package/foo/

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Thomas De Schampheleire 2014-09-18 21:39:32 +02:00 committed by Thomas Petazzoni
parent 69a5343bfb
commit a373ad0256
2 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/manual/customize-directory-structure.txt
View File

@ -40,13 +40,12 @@ it using +BR2_EXTERNAL+. Both options are valid, the choice is up to you.
| +-- <company>/ | +-- <company>/
| +-- Config.in (if not using BR2_EXTERNAL) | +-- Config.in (if not using BR2_EXTERNAL)
| +-- <company>.mk (if not using BR2_EXTERNAL) | +-- <company>.mk (if not using BR2_EXTERNAL)
| +-- <boardname>/ | +-- package1/
| +-- package1/ | | +-- Config.in
| | +-- Config.in | | +-- package1.mk
| | +-- package1.mk | +-- package2/
| +-- package2/ | +-- Config.in
| +-- Config.in | +-- package2.mk
| +-- package2.mk
| |
+-- Config.in (if using BR2_EXTERNAL) +-- Config.in (if using BR2_EXTERNAL)
+-- external.mk (if using BR2_EXTERNAL) +-- external.mk (if using BR2_EXTERNAL)

12
docs/manual/customize-outside-br.txt
View File

@ -81,19 +81,21 @@ The main usage of this is to store package recipes. The recommended
looks like: looks like:
+ +
------ ------
source "$BR2_EXTERNAL/package/<boardname>/package1/Config.in" source "$BR2_EXTERNAL/package/package1/Config.in"
source "$BR2_EXTERNAL/package/<boardname>/package2/Config.in" source "$BR2_EXTERNAL/package/package2/Config.in"
------ ------
+ +
Then, have a +$(BR2_EXTERNAL)/external.mk+ file that looks like: 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/<boardname>/package1+ and And then in +$(BR2_EXTERNAL)/package/package1+ and
+$(BR2_EXTERNAL)/package/<boardname>/package2+ create normal Buildroot +$(BR2_EXTERNAL)/package/package2+ create normal Buildroot
package recipes, as explained in xref:adding-packages[]. package recipes, as explained in xref:adding-packages[].
If you prefer, you can also group the packages in subdirectories
called <boardname> and adapt the above paths accordingly.
* One can store Buildroot defconfigs in the +configs+ subdirectory of * One can store Buildroot defconfigs in the +configs+ subdirectory of
+$(BR2_EXTERNAL)+. Buildroot will automatically show them in the +$(BR2_EXTERNAL)+. Buildroot will automatically show them in the