@@ -11,11 +11,11 @@ Some packages have been grouped by topic in a sub-directory:
one of these categories, then create your package directory in these.
New subdirectories are discouraged, however.
+Config.in+ file
-^^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~~
Then, create a file named +Config.in+. This file will contain the
option descriptions related to our +libfoo+ software that will be used
and displayed in the configuration tool. It should basically contain:
@@ -49,10 +49,13 @@ supposed to contain anything but the 'bare' name of the package.
--------------------------
source "package/libfoo/Config.in"
--------------------------
[[depends-on-vs-select]]
+Choosing +depends on+ or +select+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
The +Config.in+ file of your package must also ensure that
dependencies are enabled. Typically, Buildroot uses the following
rules:
* Use a +select+ type of dependency for dependencies on
@@ -162,11 +165,11 @@ package.
Further formatting details: see xref:writing-rules-config-in[the
coding style].
The +.mk+ file
-^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~
Finally, here's the hardest part. Create a file named +libfoo.mk+. It
describes how the package should be downloaded, configured, built,
installed, etc.