LIGCC(1) Listaller Project LIGCC(1)NAME
ligcc - Wrapper around gcc to create more portable apps
SYNOPSIS
ligcc [OPTION ...]
DESCRIPTION
This manual page documents briefly the ligcc command.
ligcc is a wrapper around gcc. It allows you to create more portable executables by doing three things:
o Forces the linker to link against older glibc symbols. Users who are using an older version of glibc will no longer get "undefined
symbol GLIBC_2.4 in /lib/libc.so"-style error messages.
o Allows you to easily statically link to any other library.
o Automatically removes bogus dependancies. For example, your program uses libfoo. libfoo uses libpng internally, but your app does not.
Yet the pkg-config file for libfoo specifies "-lfoo -lpng" is linker parameters. And tadaa - you now have a bogus dependancy on libpng!
LiGCC automatically removes the -lpng for you if your app doesn't use libpng directly.
o Add $ORIGIN/../lib to the binary's library search path. $ORIGIN is the directory in which the binary exists. This ensures that your
binary can find library dependencies which are placed in the 'lib' folder under the same prefix. You might want to install custom
libraries into /lib. If you set $APBUILD_PROJECTNAME, ligcc will also add $ORIGIN/../lib/$APBUILD_PROJECTNAME to the library search
path.
OPTIONS
See the manpage of gcc(1) for more information about possible options.
There are also several environment variables available to modify ligcc's behavior check the documentation for more information.
SEE ALSO
lig++ (1), gcc(1).
Additional documentation can be found on http://listaller.tenstral.net.
AUTHOR
This manual page was written by Matthias Klumpp matthias@tenstral.net.
COPYRIGHT
Copyright (C) 2009-2012 Matthias Klumpp
Listaller Project 20 April,2012 LIGCC(1)
Check Out this Related Man Page
DH_SHLIBDEPS(1) Debhelper DH_SHLIBDEPS(1)NAME
dh_shlibdeps - calculate shared library dependencies
SYNOPSIS
dh_shlibdeps [debhelperoptions] [-Lpackage] [-ldirectory] [-Xitem] [--params]
DESCRIPTION
dh_shlibdeps is a debhelper program that is responsible for calculating shared library dependencies for packages.
This program is merely a wrapper around dpkg-shlibdeps(1) that calls it once for each package listed in the control file, passing it a list
of ELF executables and shared libraries it has found.
OPTIONS -Xitem, --exclude=item
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.
-- params
Pass params to dpkg-shlibdeps(1).
-uparams, --dpkg-shlibdeps-params=params
This is another way to pass params to dpkg-shlibdeps(1). It is deprecated; use -- instead.
-ldirectory[:directory ...]
With recent versions of dpkg-shlibdeps, this option is generally not needed.
Before dpkg-shlibdeps is run, LD_LIBRARY_PATH will have added to it the specified directory (or directories -- separate with colons).
With recent versions of dpkg-shlibdeps, this is mostly only useful for packages that build multiple flavors of the same library, or
other situations where the library is installed into a directory not on the regular library search path.
-Lpackage, --libpackage=package
With recent versions of dpkg-shlibdeps, this option is generally not needed, unless your package builds multiple flavors of the same
library.
It tells dpkg-shlibdeps (via its -S parameter) to look first in the package build directory for the specified package, when searching
for libraries, symbol files, and shlibs files.
EXAMPLES
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:
dh_makeshlibs
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 information.
If a libbar1 package is also produced, that is an alternate build of libfoo, and is installed into /usr/lib/bar/, you can make libfoo-bin
depend on libbar1 as follows:
dh_shlibdeps -Llibbar1 -l/usr/lib/bar
SEE ALSO debhelper(7), dpkg-shlibdeps(1)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2012-09-10 DH_SHLIBDEPS(1)