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

[Nicolas Mailhot]

Le vendredi 29 avril 2005 à 15:47 +0200, Mario Lang a écrit :
> 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.

Also, at one point you might consider using distribution tools like rpm
or deb. Public repositories routinely publish packages for sets of
distributions, so at least their contributors found packaging easier
than maintaining static binaries.

Of course it depends on your app but from what you've posted static is
not really fun to achieve here.

-- 
Nicolas Mailhot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20050429/372a22fa/attachment.pgp>