manual: clarify format of comments about dependency on Linux kernel
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
8da745f04a
commit
b47c8cc8aa
|
@ -253,6 +253,22 @@ use in the comment.
|
||||||
** Dependency symbol: +!BR2_PREFER_STATIC_LIB+
|
** Dependency symbol: +!BR2_PREFER_STATIC_LIB+
|
||||||
** Comment string: +dynamic library+
|
** Comment string: +dynamic library+
|
||||||
|
|
||||||
|
Dependencies on a Linux kernel built by buildroot
|
||||||
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||||
|
Some packages need a Linux kernel to be built by buildroot. These are
|
||||||
|
typically kernel modules or firmware. A comment should be added in the
|
||||||
|
Config.in file to express this dependency, similar to dependencies on
|
||||||
|
toolchain options. The general format is:
|
||||||
|
|
||||||
|
--------------------------
|
||||||
|
foo needs a Linux kernel to be built
|
||||||
|
--------------------------
|
||||||
|
|
||||||
|
If there is a dependency on both toolchain options and the Linux
|
||||||
|
kernel, use this format:
|
||||||
|
--------------------------
|
||||||
|
foo needs a toolchain w/ featA, featB, featC and a Linux kernel to be built
|
||||||
|
--------------------------
|
||||||
|
|
||||||
The +.mk+ file
|
The +.mk+ file
|
||||||
~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~
|
||||||
|
|
Loading…
Reference in New Issue
Block a user