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>
31 lines
1.3 KiB
Plaintext
31 lines
1.3 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
== Integration with Eclipse
|
|
|
|
While a part of the embedded Linux developers like classical text
|
|
editors like Vim or Emacs, and command-line based interfaces, a number
|
|
of other embedded Linux developers like richer graphical interfaces to
|
|
do their development work. Eclipse being one of the most popular
|
|
Integrated Development Environment, Buildroot integrates with Eclipse
|
|
in order to ease the development work of Eclipse users.
|
|
|
|
Our integration with Eclipse simplifies the compilation, remote
|
|
execution and remote debugging of applications and libraries that are
|
|
built on top of a Buildroot system. It does not integrate the
|
|
Buildroot configuration and build processes themselves with
|
|
Eclipse. Therefore, the typical usage model of our Eclipse integration
|
|
would be:
|
|
|
|
* Configure your Buildroot system with +make menuconfig+, +make
|
|
xconfig+ or any other configuration interface provided with
|
|
Buildroot.
|
|
* Build your Buildroot system by running +make+.
|
|
* Start Eclipse to develop, execute and debug your own custom
|
|
applications and libraries, that will rely on the libraries built
|
|
and installed by Buildroot.
|
|
|
|
The Buildroot Eclipse integration installation process and usage is
|
|
described in detail at
|
|
https://github.com/mbats/eclipse-buildroot-bundle/wiki.
|