doc/manual.txt: add a section about development packages.
This commit is contained in:
parent
49e6e841ae
commit
9cc3d33324
|
@ -100,6 +100,23 @@ All subpackages need an additional symlink to the `main` pkg, i.e:
|
|||
Otherwise dependencies requiring those packages won't find its `template`
|
||||
file.
|
||||
|
||||
Development packages
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
A development package, commonly generated as a subpackage, shall only contain
|
||||
files required for development, that is, headers, static libraries, shared
|
||||
library symlinks, pkg-config files, API documentation or any other script
|
||||
that is only useful when developping for the target software.
|
||||
|
||||
A development package should depend on packages that are required to link
|
||||
against the provided shared libraries, i.e if `libfoo` provides the
|
||||
`libfoo.so.2` shared library and the linking needs `-lbar`, the package
|
||||
providing the `libbar` shared library should be added as a dependency;
|
||||
and most likely it shall depend on its development package.
|
||||
|
||||
If a development package provides a `pkg-config` file, you should verify
|
||||
what dependencies the package needs for dynamic or static linking, and add
|
||||
the appropiate `development` packages as dependencies.
|
||||
|
||||
Package build phases
|
||||
--------------------
|
||||
Building a package consist of the following phases:
|
||||
|
|
Loading…
Reference in New Issue