From b47c8cc8aa51a6fd3de8a60c5090c39801c81afd Mon Sep 17 00:00:00 2001 From: Thomas De Schampheleire Date: Sun, 15 Dec 2013 13:20:40 +0100 Subject: [PATCH] manual: clarify format of comments about dependency on Linux kernel Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard --- docs/manual/adding-packages-directory.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt index 36b709308c..57f3204412 100644 --- a/docs/manual/adding-packages-directory.txt +++ b/docs/manual/adding-packages-directory.txt @@ -253,6 +253,22 @@ use in the comment. ** Dependency symbol: +!BR2_PREFER_STATIC_LIB+ ** 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 ~~~~~~~~~~~~~~ -- 2.30.2