docs/manual: slightly compactify a paragraph
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
parent
aee8dc79a6
commit
04d8fee3d7
@ -39,12 +39,11 @@ itself should be indented with one tab and two spaces, lines should
|
||||
not be longer than 72 columns, and it must mention the upstream URL
|
||||
of the project.
|
||||
|
||||
You can add other sub-options into a +if
|
||||
BR2_PACKAGE_LIBFOO...endif+ statement to configure particular things
|
||||
in your software. You can look at examples in other packages. The
|
||||
syntax of the +Config.in+ file is the same as the one for the kernel
|
||||
Kconfig file. The documentation for this syntax is available at
|
||||
http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[]
|
||||
You can add other sub-options into a +if BR2_PACKAGE_LIBFOO...endif+
|
||||
statement to configure particular things in your software. You can look at
|
||||
examples in other packages. The syntax of the +Config.in+ file is the same
|
||||
as the one for the kernel Kconfig file. The documentation for this syntax is
|
||||
available at http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[]
|
||||
|
||||
Finally you have to add your new +libfoo/Config.in+ to
|
||||
+package/Config.in+ (or in a category subdirectory if you decided to
|
||||
|
Loading…
Reference in New Issue
Block a user