docs/manual/adding-packages-directory.txt

4 === Package directory
6 First of all, create a directory under the +package+ directory for
10 +x11r7+, +qt5+ and +gstreamer+. If your package fits in
11 one of these categories, then create your package directory in these.
16 For the package to be displayed in the configuration tool, you need to
17 create a Config file in your package directory. There are two types:
62 +package/Config.in+ (or in a category subdirectory if you decided to
63 put your package in one of the existing categories). The files
65 supposed to contain anything but the 'bare' name of the package.
68 source "package/libfoo/Config.in"
77 * The host package is only required to satisfy build-time
79   +host-foo+ to the target package's +BAR_DEPENDENCIES+ variable. No
82 * The host package should be explicitly selectable by the user from
84   for that host package:
98 +package/Config.in.host+. The files included there are 'sorted alphabetically'
99 and are 'NOT' supposed to contain anything but the 'bare' name of the package.
102 source "package/foo/Config.in.host"
105 The host package will then be available from the +Host utilities+ menu.
110 The +Config.in+ file of your package must also ensure that
117   dependencies are selected. For example, the _libgtk2_ package uses
134 possible to select a package, whom one of its dependencies/requirement
165         bool "Package A"
168         bool "Package B"
172         bool "Package C"
176         bool "Package D"
180         bool "Package E"
184 * Selecting +Package C+ will be visible if +Package B+ has been
185   selected, which in turn is only visible if +Package A+ has been
188 * Selecting +Package E+ will select +Package D+, which will select
189   +Package B+, it will not check for the dependencies of +Package B+,
190   so it will not select +Package A+.
192 * Since +Package B+ is selected but +Package A+ is not, this violates
193   the dependency of +Package B+ on +Package A+. Therefore, in such a
198 	bool "Package D"
203 	bool "Package E"
208 Overall, for package library dependencies, +select+ should be
212 is also enabled, but not necessarily built before your package. To do
214 package.
230 not enabled, so that the user knows why the package is not available.
238 that all other dependencies of the package (including dependencies on
244 the main package) it is preferable to have a global +if ... endif+
248 The general format of a dependency +comment+ for package foo is:
311 ** Note that it is usually not the package itself that has a minimum
312    host GCC version, but rather a host-package on which it depends.
374 If a package needs udev /dev management, it should depend on symbol
390 Some features can be provided by more than one package, such as the
393 See xref:virtual-package-tutorial[] for more on the virtual packages.
400 describes how the package should be downloaded, configured, built,
403 Depending on the package type, the +.mk+ file must be written in a
410   compilation and installation of the package. This
414   them through in a xref:generic-package-tutorial[tutorial] and a
415   xref:generic-package-reference[reference].
421   system. We cover them through a xref:autotools-package-tutorial[tutorial]
422   and xref:autotools-package-reference[reference].
428    CMake. We cover them through a xref:cmake-package-tutorial[tutorial]
429    and xref:cmake-package-reference[reference].
434    xref:python-package-tutorial[tutorial] and a
435    xref:python-package-reference[reference].
439    through a xref:luarocks-package-tutorial[tutorial] and a
440    xref:luarocks-package-reference[reference].
450 package. The only reason for not adding a +.hash+ file is when hash
451 checking is not possible due to how the package is downloaded.
453 When a package has a version selection choice, then the hash file may be
455 +package/libfoo/1.2.3/libfoo.hash+. This is especially important if the
457 in the same file. Otherwise, the hash file should stay in the package's
498 package version is bumped. The hashes are checked during the make legal-info
499 target run. For a package with multiple versions (like Qt5),
500 create the hash file in a subdirectory +<packageversion>+ of that package
554 locally to the package folder.