Documentation< Previous | Contents | Next >
9.1.2. Installing Build Dependencies
Now that you have the sources, you still need to install build dependencies. They will be necessary to build the desired binary packages but are also likely required for partial builds that you might want to run to test the changes while you make them.
Each source package declares its build dependencies in the Build-Depends field of the debian/ control file. Let’s instruct apt to install those (assuming that you are in a directory containing an unpacked source package):
$ sudo apt build-dep ./
Note, using directory ’./’ to get the build dependencies Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
autoconf automake autopoint autotools-dev debhelper dh-autoreconf
dh-strip-nondeterminism gettext intltool-debian libarchive-zip-perl libfile-stripnondeterminism-perl libtool po-debconf
0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded. Need to get 4 456 kB of archives.
After this operation, 14,6 MB of additional disk space will be used. Do you want to continue? [Y/n]
[…]
$ sudo apt build-dep ./
Note, using directory ’./’ to get the build dependencies Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
autoconf automake autopoint autotools-dev debhelper dh-autoreconf
dh-strip-nondeterminism gettext intltool-debian libarchive-zip-perl libfile-stripnondeterminism-perl libtool po-debconf
0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded. Need to get 4 456 kB of archives.
After this operation, 14,6 MB of additional disk space will be used. Do you want to continue? [Y/n]
[…]
In this sample, all build dependencies can be satisfied with packages available to APT. This might not always be the case as the tool building kali-rolling does not ensure installability of build de- pendencies (only dependencies of binary packages are taken into account). In practice, binary dependencies and build dependencies are often tightly coupled and most packages will have their build dependencies satisfiable.