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>
142 lines
3.4 KiB
Plaintext
142 lines
3.4 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
== Coding style
|
|
|
|
Overall, these coding style rules are here to help you to add new files in
|
|
Buildroot or refactor existing ones.
|
|
|
|
If you slightly modify some existing file, the important thing is
|
|
to keep the consistency of the whole file, so you can:
|
|
|
|
* either follow the potentially deprecated coding style used in this
|
|
file,
|
|
|
|
* or entirely rework it in order to make it comply with these rules.
|
|
|
|
[[writing-rules-config-in]]
|
|
|
|
=== +Config.in+ file
|
|
|
|
+Config.in+ files contain entries for almost anything configurable in
|
|
Buildroot.
|
|
|
|
An entry has the following pattern:
|
|
|
|
---------------------
|
|
config BR2_PACKAGE_LIBFOO
|
|
bool "libfoo"
|
|
depends on BR2_PACKAGE_LIBBAZ
|
|
select BR2_PACKAGE_LIBBAR
|
|
help
|
|
This is a comment that explains what libfoo is.
|
|
|
|
http://foosoftware.org/libfoo/
|
|
---------------------
|
|
|
|
* The +bool+, +depends on+, +select+ and +help+ lines are indented
|
|
with one tab.
|
|
|
|
* The help text itself should be indented with one tab and two
|
|
spaces.
|
|
|
|
The +Config.in+ files are the input for the configuration tool
|
|
used in Buildroot, which is the regular _Kconfig_. For further
|
|
details about the _Kconfig_ language, refer to
|
|
http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[].
|
|
|
|
[[writing-rules-mk]]
|
|
|
|
=== The +.mk+ file
|
|
|
|
* Header: The file starts with a header. It contains the module name,
|
|
preferably in lowercase, enclosed between separators made of 80 hashes. A
|
|
blank line is mandatory after the header:
|
|
+
|
|
---------------------
|
|
################################################################################
|
|
#
|
|
# libfoo
|
|
#
|
|
################################################################################
|
|
---------------------
|
|
+
|
|
* Assignment: use +=+ preceded and followed by one space:
|
|
+
|
|
---------------------
|
|
LIBFOO_VERSION = 1.0
|
|
LIBFOO_CONF_OPT += --without-python-support
|
|
---------------------
|
|
+
|
|
Do not align the +=+ signs.
|
|
|
|
* Indentation: use tab only:
|
|
+
|
|
---------------------
|
|
define LIBFOO_REMOVE_DOC
|
|
$(RM) -fr $(TARGET_DIR)/usr/share/libfoo/doc \
|
|
$(TARGET_DIR)/usr/share/man/man3/libfoo*
|
|
endef
|
|
---------------------
|
|
+
|
|
Note that commands inside a +define+ block should always start with a tab,
|
|
so _make_ recognizes them as commands.
|
|
|
|
* Optional dependency:
|
|
|
|
** Prefer multi-line syntax.
|
|
+
|
|
YES:
|
|
+
|
|
---------------------
|
|
ifeq ($(BR2_PACKAGE_PYTHON),y)
|
|
LIBFOO_CONF_OPT += --with-python-support
|
|
LIBFOO_DEPENDENCIES += python
|
|
else
|
|
LIBFOO_CONF_OPT += --without-python-support
|
|
endif
|
|
---------------------
|
|
+
|
|
NO:
|
|
+
|
|
---------------------
|
|
LIBFOO_CONF_OPT += --with$(if $(BR2_PACKAGE_PYTHON),,out)-python-support
|
|
LIBFOO_DEPENDENCIES += $(if $(BR2_PACKAGE_PYTHON),python,)
|
|
---------------------
|
|
|
|
** Keep configure options and dependencies close together.
|
|
|
|
* Optional hooks: keep hook definition and assignment together in one
|
|
if block.
|
|
+
|
|
YES:
|
|
+
|
|
---------------------
|
|
ifneq ($(BR2_LIBFOO_INSTALL_DATA),y)
|
|
define LIBFOO_REMOVE_DATA
|
|
$(RM) -fr $(TARGET_DIR)/usr/share/libfoo/data
|
|
endef
|
|
LIBFOO_POST_INSTALL_TARGET_HOOKS += LIBFOO_REMOVE_DATA
|
|
endif
|
|
---------------------
|
|
+
|
|
NO:
|
|
+
|
|
---------------------
|
|
define LIBFOO_REMOVE_DATA
|
|
$(RM) -fr $(TARGET_DIR)/usr/share/libfoo/data
|
|
endef
|
|
|
|
ifneq ($(BR2_LIBFOO_INSTALL_DATA),y)
|
|
LIBFOO_POST_INSTALL_TARGET_HOOKS += LIBFOO_REMOVE_DATA
|
|
endif
|
|
---------------------
|
|
|
|
=== The documentation
|
|
|
|
The documentation uses the
|
|
http://www.methods.co.nz/asciidoc/[asciidoc] format.
|
|
|
|
For further details about the http://www.methods.co.nz/asciidoc/[asciidoc]
|
|
syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[].
|