From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 2 for 2014.08] manual/user guide/customization: expand introduction text
Date: Wed, 27 Aug 2014 21:40:10 +0200 [thread overview]
Message-ID: <e21c7854621143b573bf.1409168410@localhost> (raw)
In-Reply-To: <patchbomb.1409168409@localhost>
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: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
docs/manual/customize.txt | 25 +++++++++++++++++++++----
1 files changed, 21 insertions(+), 4 deletions(-)
diff --git a/docs/manual/customize.txt b/docs/manual/customize.txt
--- a/docs/manual/customize.txt
+++ b/docs/manual/customize.txt
@@ -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 from a clean buildroot tree. By
+following the recommended strategy, you can even use the same Buildroot
+tree to build multiple distinct projects!
include::customize-rootfs.txt[]
next prev parent reply other threads:[~2014-08-27 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 19:40 [Buildroot] [PATCH 0 of 2 for 2014.08] Manual improvements part 4 Thomas De Schampheleire
2014-08-27 19:40 ` Thomas De Schampheleire [this message]
2014-08-27 20:22 ` [Buildroot] [PATCH 1 of 2 for 2014.08] manual/user guide/customization: expand introduction text Samuel Martin
2014-08-28 6:56 ` Thomas De Schampheleire
2014-08-27 19:40 ` [Buildroot] [PATCH 2 of 2 for 2014.08] manual/user guide/customization: add section with recommended dir structure Thomas De Schampheleire
2014-08-27 20:29 ` Samuel Martin
2014-08-28 6:59 ` Thomas De Schampheleire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e21c7854621143b573bf.1409168410@localhost \
--to=patrickdepinguin@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.