[linux-audio-dev] producing a self-contained executable

Mario Lang mlang at delysid.org
Fri Apr 29 13:47:52 UTC 2005


Florian Schmidt <mista.tapas at gmx.net> writes:

> On Fri, 29 Apr 2005 12:38:24 +0200
> Tom Szilagyi <tszilagyi at users.sourceforge.net> wrote:
>
>> I've run into difficulties trying to compile a statically linked
>> version due to problems with GTK, which apparently doesn't allow me to
>> statically link to it. I also don't really know how to get at
>> statically linking libc (however I didn't try very hard anyway, since
>> I already got stuck with GTK).
>> 
>
> Hi,
>
> i don't know much about statically linking either, but if it doesn't
> work at all you might want to distribute the (shared) libs in your
> package, and then use a script to startup the app which sets the
> LD_LIBRARY_PATH to the dir which holds the libs from your package.

Depending on how the program works with input/output files,
a chrooted installation is probably even more robust.

-- 
CYa,
  Mario



More information about the Linux-audio-dev mailing list