Hi,
On Fri, 4 Aug 2006, Patrik Gfeller <gfellerpatrik@...> wrote:
> Hi all,
>
> Unfortunately I did not figure out how to build libvncserver as .so
> (so it dynamically links libc, zlib & libjpeg ); is it possible to
> do so? And if yes, what do I have to do - or where can I find hints
> on how to do this?
I don't think we have a way to do this via the configure, we probably
should add it...
Here is a manual/kludgy way to do it:
# env CFLAGS="-fPIC" ./configure; make
# cd libvncserver
# rm libvncserver.a
# make
On last last make it will rebuild libvncserver.a, take note of the command
and by cutting and pasting change the:
/usr/bin/ar cru libvncserver.a
to
cc -shared -o libvncserver.so
e.g.:
# cc -shared -o libvncserver.so main.o rfbserver.o rfbregion.o auth.o sockets.o stats.o corre.o hextile.o rre.o translate.o cutpaste.o httpd.o cursor.o font.o draw.o selbox.o d3des.o vncauth.o cargs.o minilzo.o ultra.o scale.o zlib.o zrle.o zrleoutstream.o zrlepalettehelper.o tight.o rfbtightserver.o handlefiletransferrequest.o filetransfermsg.o filelistinfo.o
> as I use libvncserver (0.8.2) in an embedded environment (iPAQ running
> Linux) I try to slim down the size of my app as much as possible;
> therefore I thought it would make sense to use shared object files
> instead of statically linking with libvncserver.
I don't think this will yield any advantage unless you are shipping more
than one binary, or have more than one process running at the same time.
But perhaps you are, so then it would help to use libvncserver.so.
Karl
|