Commit a194faa4 authored by Thomas De Schampheleire's avatar Thomas De Schampheleire Committed by Peter Korsgaard
Browse files

manual/user guide/customization: expand introduction text 



This patch expands the introduction text of chapter 'Project-specific
customization' by listing the type of customizations that can be performed
by a project.

Signed-off-by: default avatarThomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: default avatarPeter Korsgaard <peter@korsgaard.com>
parent f4905d7a

docs/manual/customize.txt

+21 −4
Original line number Diff line number Diff line
@@ -3,11 +3,28 @@ 


== Project-specific customization



The following sections describe the various way in which you can

customize Buildroot for a given project.

Typical actions you may need to perform for a given project are:



For instructions on how to add new packages to Buildroot, refer to

xref:adding-packages[]

- configuring Buildroot (including build options and toolchain,

  bootloader, kernel, package and filesystem image type selection)

- configuring other components, like the Linux kernel and BusyBox

- adding project-specific patches to some packages (using

  +BR2_GLOBAL_PATCH_DIR+)

- adding or overwriting files on the target filesystem (using

  +BR2_ROOTFS_OVERLAY+)

- modifying or deleting files on the target filesystem (using

  +BR2_ROOTFS_POST_BUILD_SCRIPT+)

- running arbitrary commands prior to generating the filesystem image

  (using +BR2_ROOTFS_POST_BUILD_SCRIPT+)

- running arbitrary commands after generating the filesystem image

  (using +BR2_ROOTFS_POST_IMAGE_SCRIPT+)

- adding project-specific packages



This chapter describes how to make such project-specific customizations

in Buildroot and how to store them in a way that you can build the same

image in a reproducible way, even after running 'make clean'. By

following the recommended strategy, you can even use the same Buildroot

tree to build multiple distinct projects!



include::customize-rootfs.txt[]