Exclude files that contain ``item'' anywhere in their filename from being
passed to dpkg-shlibdeps. This will make their dependencies be ignored.
This may be useful in some situations, but use it with caution. This option
may be used more than once to exclude more than one thing.
Before dpkg-shlibdeps is run, LD_LIBRARY_PATH will have added to it the
specified directory (or directories --- separate with colons). This is
useful for multi-binary packages where a library is built in one
package and another package contains binaries linked against said
library. Relative paths will be made absolute for the benefit of
Note that the directory given should be the complete or relative path to
a directory that contains the library. See example below.
Use the shlibs file automatically generated by dh_makeshlibs for the named
package as a kind of automatically generated shlibs.local file. You can use
this switch in concert with the -l switch to make dpkg-shlibdeps find a
library built as part of the current package, and get the shlibs information.
See example below.
Suppose that your source package produces libfoo1, libfoo-dev, and
libfoo-bin binary packages. libfoo-bin links against libfoo1, and should
depend on it. In your rules file, first run dh_makeshlibs, then dh_shlibdeps:
This will have the effect of generating automatically a shlibs file for
libfoo1, and using that file and the libfoo1 library in the
debian/libfoo1/usr/lib directory to calculate shared library dependency