2012-11-11 04:14:43 +01:00
|
|
|
// -*- mode:doc; -*-
|
2013-02-13 13:59:02 +01:00
|
|
|
// vim: set syntax=asciidoc:
|
2012-11-11 04:14:43 +01:00
|
|
|
|
manual: use one-line titles instead of two-line titles (trivial)
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>
2014-05-02 07:47:30 +02:00
|
|
|
= About Buildroot
|
2011-10-10 10:46:39 +02:00
|
|
|
|
2012-12-29 05:42:28 +01:00
|
|
|
Buildroot is a tool that simplifies and automates the process of
|
|
|
|
building a complete Linux system for an embedded system, using
|
|
|
|
cross-compilation.
|
|
|
|
|
|
|
|
In order to achieve this, Buildroot is able to generate a
|
|
|
|
cross-compilation toolchain, a root filesystem, a Linux kernel image
|
|
|
|
and a bootloader for your target. Buildroot can be used for any
|
|
|
|
combination of these options, independently (you can for example use
|
|
|
|
an existing cross-compilation toolchain, and build only your root
|
|
|
|
filesystem with Buildroot).
|
2011-10-10 10:46:39 +02:00
|
|
|
|
|
|
|
Buildroot is useful mainly for people working with embedded systems.
|
|
|
|
Embedded systems often use processors that are not the regular x86
|
|
|
|
processors everyone is used to having in his PC. They can be PowerPC
|
|
|
|
processors, MIPS processors, ARM processors, etc.
|
|
|
|
|
2012-11-11 04:14:43 +01:00
|
|
|
Buildroot supports numerous processors and their variants; it also
|
2012-11-16 05:54:19 +01:00
|
|
|
comes with default configurations for several boards available
|
|
|
|
off-the-shelf. Besides this, a number of third-party projects are based on,
|
2012-11-27 12:59:16 +01:00
|
|
|
or develop their BSP footnote:[BSP: Board Support Package] or
|
|
|
|
SDK footnote:[SDK: Software Development Kit] on top of Buildroot.
|