86a415df8a
Asciidoc supports two syntaxes for section titles: two-line titles (title
plus underline consisting of a particular symbol), and one-line titles
(title prefixed with a specific number of = signs).
The two-line title underlines are:
Level 0 (top level): ======================
Level 1: ----------------------
Level 2: ~~~~~~~~~~~~~~~~~~~~~~
Level 3: ^^^^^^^^^^^^^^^^^^^^^^
Level 4 (bottom level): ++++++++++++++++++++++
and the one-line title prefixes:
= Document Title (level 0) =
== Section title (level 1) ==
=== Section title (level 2) ===
==== Section title (level 3) ====
===== Section title (level 4) =====
The buildroot manual is currenly using the two-line titles, but this has
multiple disadvantages:
- asciidoc also uses some of the underline symbols for other purposes (like
preformatted code, example blocks, ...), which makes it difficult to do
mass replacements, such as a planned follow-up patch that needs to move
all sections one level down.
- it is difficult to remember which level a given underline symbol (=-~^+)
corresponds to, while counting = signs is easy.
This patch changes all two-level titles to one-level titles in the manual.
The bulk of the change was done with the following Python script, except for
the level 1 titles (-----) as these underlines are also used for literal
code blocks.
This patch only changes the titles, no other changes. In
adding-packages-directory.txt, I did add missing newlines between some
titles and their content.
----------------------------------------------------------------------------
#!/usr/bin/env python
import sys
import mmap
import re
for input in sys.argv[1:]:
f = open(input, 'r+')
f.flush()
s = mmap.mmap(f.fileno(), 0)
# Level 0 (top level): ====================== =
# Level 1: ---------------------- ==
# Level 2: ~~~~~~~~~~~~~~~~~~~~~~ ===
# Level 3: ^^^^^^^^^^^^^^^^^^^^^^ ====
# Level 4 (bottom level): ++++++++++++++++++++++ =====
def replace_title(s, symbol, replacement):
pattern = re.compile(r'(.+\n)\%s{2,}\n' % symbol, re.MULTILINE)
return pattern.sub(r'%s \1' % replacement, s)
new = s
new = replace_title(new, '=', '=')
new = replace_title(new, '+', '=====')
new = replace_title(new, '^', '====')
new = replace_title(new, '~', '===')
#new = replace_title(new, '-', '==')
s.seek(0)
s.write(new)
s.resize(s.tell())
s.close()
f.close()
----------------------------------------------------------------------------
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
116 lines
4.3 KiB
Plaintext
116 lines
4.3 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
== Using Buildroot
|
|
|
|
Buildroot has a nice configuration tool similar to the one you can
|
|
find in the http://www.kernel.org/[Linux kernel] or in
|
|
http://www.busybox.net/[Busybox]. Note that you can *and should build
|
|
everything as a normal user*. There is no need to be root to configure
|
|
and use Buildroot. The first step is to run the configuration
|
|
assistant:
|
|
|
|
--------------------
|
|
$ make menuconfig
|
|
--------------------
|
|
|
|
or
|
|
|
|
--------------------
|
|
$ make nconfig
|
|
--------------------
|
|
|
|
to run the old or new curses-based configurator, or
|
|
|
|
--------------------
|
|
$ make xconfig
|
|
--------------------
|
|
|
|
or
|
|
|
|
--------------------
|
|
$ make gconfig
|
|
--------------------
|
|
|
|
to run the Qt or GTK-based configurators.
|
|
|
|
All of these "make" commands will need to build a configuration
|
|
utility (including the interface), so you may need to install
|
|
"development" packages for relevant libraries used by the
|
|
configuration utilities. Check xref:requirement[] to know what
|
|
Buildroot needs, and specifically the xref:requirement-optional[optional requirements]
|
|
to get the dependencies of your favorite interface.
|
|
|
|
For each menu entry in the configuration tool, you can find associated
|
|
help that describes the purpose of the entry.
|
|
|
|
Once everything is configured, the configuration tool generates a
|
|
+.config+ file that contains the description of your
|
|
configuration. It will be used by the Makefiles to do what's needed.
|
|
|
|
Let's go:
|
|
|
|
--------------------
|
|
$ make
|
|
--------------------
|
|
|
|
You *should never* use +make -jN+ with Buildroot: it does not support
|
|
'top-level parallel make'. Instead, use the +BR2_JLEVEL+ option to
|
|
tell Buildroot to run each package compilation with +make -jN+.
|
|
|
|
The `make` command will generally perform the following steps:
|
|
|
|
* download source files (as required);
|
|
* configure, build and install the cross-compiling toolchain using the
|
|
appropriate toolchain backend, or simply import an external toolchain;
|
|
* build/install selected target packages;
|
|
* build a kernel image, if selected;
|
|
* build a bootloader image, if selected;
|
|
* create a root filesystem in selected formats.
|
|
|
|
Buildroot output is stored in a single directory, +output/+.
|
|
This directory contains several subdirectories:
|
|
|
|
* +images/+ where all the images (kernel image, bootloader and root
|
|
filesystem images) are stored.
|
|
|
|
* +build/+ where all the components are built
|
|
(this includes tools needed to run Buildroot on
|
|
the host and packages compiled for the target). The +build/+
|
|
directory contains one subdirectory for each of these components.
|
|
|
|
* +staging/+ which contains a hierarchy similar to a root filesystem
|
|
hierarchy. This directory contains the installation of the
|
|
cross-compilation toolchain and all the userspace packages selected
|
|
for the target. However, this directory is 'not' intended to be
|
|
the root filesystem for the target: it contains a lot of development
|
|
files, unstripped binaries and libraries that make it far too big
|
|
for an embedded system. These development files are used to compile
|
|
libraries and applications for the target that depend on other
|
|
libraries.
|
|
|
|
* +target/+ which contains 'almost' the complete root filesystem for
|
|
the target: everything needed is present except the device files in
|
|
+/dev/+ (Buildroot can't create them because Buildroot doesn't run
|
|
as root and doesn't want to run as root). Also, it doesn't have the correct
|
|
permissions (e.g. setuid for the busybox binary). Therefore, this directory
|
|
*should not be used on your target*. Instead, you should use one of
|
|
the images built in the +images/+ directory. If you need an
|
|
extracted image of the root filesystem for booting over NFS, then
|
|
use the tarball image generated in +images/+ and extract it as
|
|
root. Compared to +staging/+, +target/+ contains only the files and
|
|
libraries needed to run the selected target applications: the
|
|
development files (headers, etc.) are not present, the binaries are
|
|
stripped.
|
|
|
|
* +host/+ contains the installation of tools compiled for the host
|
|
that are needed for the proper execution of Buildroot, including the
|
|
cross-compilation toolchain.
|
|
|
|
These commands, +make menuconfig|nconfig|gconfig|xconfig+ and +make+, are the
|
|
basic ones that allow to easily and quickly generate images fitting
|
|
your needs, with all the supports and applications you enabled.
|
|
|
|
More details about the "make" command usage are given in
|
|
xref:make-tips[].
|