[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Backporting the "dh_shlibdeps -L" option.

On Mon, Dec 16, 2002 at 11:59:37AM +1100, Brian May wrote:
> On Mon, Dec 16, 2002 at 04:47:57AM +1100, Andrew Lau wrote:
> > dh_makeshlibs
> > dh_shlibdeps -L libgcm0 -l debian/libgcm0/usr/lib
> What does the -L parameter do?

From DH_SHLIBDEPS(1) - v4.1.28

       -Lpackage, --libpackage=package

	Use the shlibs file automatically generated by dh_makeshlibs
	for the named package as a kind of automatically generated
	shlibs.local file. You can us 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. lib-foo-bin links against libfoo1, and
should depend on it. In your rules file, first run dh_makeshlibs, then

               dh_shlibdeps -L libfoo1 -l debian/libfoo1/usr/lib

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 information.

Yours sincerely,
Andrew "Netsnipe" Lau

* Andrew "Netsnipe" Lau              Computer Science & Student Rep, UNSW *
*   # apt-get into it                 Debian GNU/Linux Package Maintainer *
*     <netsnipe(+)debianplanet.org\0>      <alau(+)cse.unsw.edu.au\0>     *
* GnuPG 1024D/2E8B68BD 0B77 73D0 4F3B F286 63F1  9F4A 9B24 C07D 2E8B 68BD *

Attachment: pgpbI8huphlGB.pgp
Description: PGP signature

Reply to: