depscan(1) [debian man page]

DEPSCAN(1)							 Listaller Project							DEPSCAN(1)

NAME

       depscan - Detect binary dependencies

SYNOPSIS

       depscan [OPTION ...]

DESCRIPTION

       This manual page documents briefly the depscan command.

       depscan reads library dependencies of binary files in a directory and ouputs them in form of a list.

OPTIONS

       -r, --recursive
	   Search for binaries in recursive mode.

       --simpletext
	   Output simple, machine-readable text.

       --version
	   Display version number of depscan

       --verbose
	   Turn on verbose mode (this can be used for debugging).

SEE ALSO

       lipkgen (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						   18 April,2012							DEPSCAN(1)

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)