docs/manual: remove FAQ entry about 'depends on' vs. 'select'
The FAQ is before the section on package development, and only covers user issues, not developer issues, so the FAQ entry about 'depends on' vs. 'select' really doesn't have its place here. And the 'depends on' vs. 'select' issue is already covered in a later section, see http://buildroot.org/downloads/manual/manual.html#depends-on-vs-select. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
parent
401d323698
commit
163ec17904
@ -89,17 +89,6 @@ If you need documentation data on your target anyway, then Buildroot
|
|||||||
is not suitable for your purpose, and you should look for a _real
|
is not suitable for your purpose, and you should look for a _real
|
||||||
distribution_ (see: xref:faq-no-compiler-on-target[]).
|
distribution_ (see: xref:faq-no-compiler-on-target[]).
|
||||||
|
|
||||||
[[faq-depends-on-vs-select]]
|
|
||||||
+Config.in+: _depends on_ vs _select_
|
|
||||||
-------------------------------------
|
|
||||||
|
|
||||||
When adding a new package to Buildroot, you will most likely have to
|
|
||||||
deal with expressing the dependencies of this package.
|
|
||||||
|
|
||||||
In the +Config.in+ file, dependencies may be expressed following two
|
|
||||||
semantics.
|
|
||||||
See xref:depends-on-vs-select[choosing between _depends_ and _select_].
|
|
||||||
|
|
||||||
[[faq-why-not-visible-package]]
|
[[faq-why-not-visible-package]]
|
||||||
Why are some packages not visible in the Buildroot config menu?
|
Why are some packages not visible in the Buildroot config menu?
|
||||||
---------------------------------------------------------------
|
---------------------------------------------------------------
|
||||||
|
Loading…
Reference in New Issue
Block a user