summaryrefslogtreecommitdiffstats
path: root/docs/manual/customize-directory-structure.txt
Commit message (Collapse)AuthorAgeFilesLines
* docs/manual: add external.desc to list of files needed for BR2_EXTERNALPhilipp Wagner2018-11-021-0/+1
| | | | | | | | | | | | external.desc must be present when using a br2-external tree. The documentation notes this later in the text, but the file is missing from the initial overview of files. Fixes bug #11481. Signed-off-by: Philipp Wagner <mail@philipp-wagner.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* docs/manual: document the br2-external NAMEYann E. MORIN2016-10-161-6/+7
| | | | | | | | | | | | | | | | | | | | | | Update the manual with the new external.desc mandatory file. Take the opportunity to add a section listing all mandatory files, Config.in, external.mk and the new external.desc, instead of just hinting about them in the external package recipes section. Change the examples to use the NAME-suffixed variable instead of the raw BR2_EXTERNAL variable. Change all references to BR2_EXTERNAL elsewhere in the manual to now use the 'br2-external tree' terminology. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Samuel Martin <s.martin49@gmail.com> Cc: Romain Naour <romain.naour@openwide.fr> Cc: Julien CORJON <corjon.j@ecagroup.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* manual/user guide/customization: add section on layered customizationThomas De Schampheleire2014-09-211-0/+51
| | | | | | | | | Inspired by some text in the 'project-specific patches' section, this patch adds a separate section on layering customizations by providing multiple post-build scripts, multiple rootfs overlays, etc. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* manual/user guide/customization: change recommendation for package pathsThomas De Schampheleire2014-09-211-7/+6
| | | | | | | | | | | | | | | | | | 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>
* manual/user guide/customization: rework section on BR2_EXTERNALThomas De Schampheleire2014-08-301-0/+1
| | | | | | | | | | | | This patch reworks the section on BR2_EXTERNAL as follows: - move note about upstreaming to the chapter introduction - streamline the section with the previously added section 'Recommended directory structure', avoiding duplication. - use $(BR2_EXTERNAL) rather than BR2_EXTERNAL when referring to file paths. - some general rewording Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* manual/user guide/customization: add section with recommended dir structureThomas De Schampheleire2014-08-301-0/+58
Although the user is free to choose where to put project-specific files, the presentation 'Using Buildroot for real projects' [1] first described a certain recommendation. This patch briefly describes this recommendation in the form of a directory structure overview, the details will be added in subsequent patches. Since the section on BR2_EXTERNAL is logically connected to the directory structure, this section is moved right after it. [1] http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
OpenPOWER on IntegriCloud