leetNightshade
/
help-center-docs
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix headers for Build dependencies in Packaging Practices.

This commit is contained in:
Joshua Strobl 2017-03-16 17:18:49 +02:00
parent b6ac25c2e9
commit 3851a578c5
No known key found for this signature in database
GPG Key ID: 3F6FD9A6B13E584D
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
packaging/packaging-practices/en.md
View File

@ -137,7 +137,7 @@ This is an example of installing a custom profile file, seen in the `bash` packa
install -m 0644 $pkgfiles/profile $installdir/etc/profile
```
### Build dependencies
## Build dependencies
Most software packages that you build will in one way or another, depend on another software package to provide specific functionality. This is usually achieved by using a library.
@ -154,7 +154,7 @@ the package providing that dependency, you simply list the same name. Any packag
A secondary advantage is that this allows for easily switching or replacing a providing package. When no `pkgconfig` name is available (some packages do not provide these, or it doesn’t make sense for them to), you
may use the explicit package name. Always ensure you select the correct package, i.e. the `-devel` subpackage. This provides the necessary symlinks and headers to build packages.
#### Using pkgconfig dependencies
### Using pkgconfig dependencies
In the `builddeps` list, simply use the `pkgconfig(name)` syntax. For example, to add gtk+-3.0 to the build dependencies, we would do the following: