nanogui: Thread: Static or Shared ?

A rather trivial question but -
I am working (along with Amit here) on a C based widget set for nano-X. Should
I make my library a shared one so that only one copy is loaded at runtime ?
Any issues with this ? 
Why is libnano-X static & not shared ?

On Sat, 27 Jan 2001, Sunil Soman wrote:
> A rather trivial question but -
> I am working (along with Amit here) on a C based widget set for nano-X. Should
> I make my library a shared one so that only one copy is loaded at runtime ?

It shouldn't be difficult to do either. Shared libraries are a big win on
systems which support them, but obviously it'd be nice if you can build
statically too for systems like ucLinux which don't have shared library
support.

> Why is libnano-X static & not shared ?

Partially historic, partially to make it easier to test without needing to
install the libraries (if you use shared libraries and don't install them
to the system locations, you need to specify their location explicitly
at runtime with LD_LIBRARY_PATH). It does seem to work fine when you turn
SHAREDLIBS on in the config (apart from one program which refuses to
build due to a makefile bug which makes it still want to link against the 
static libraries), and the resulting applications end up a lot smaller as 
a result.

-- 
------- Alex Holden -------
http://www.linuxhacker.org/
 http://www.robogeeks.org/

I think that Greg has worked all the bugs out for the shared libaries. 
The most important thing is that we make it easy to go shared / static,
since
shared is better for a operating environment, but static is much better
for a development environment, especially if you are using more than 1
microwindows tree at a time.

Jordan

Alex Holden wrote:
>
> > Why is libnano-X static & not shared ?
> 
> Partially historic, partially to make it easier to test without needing to
> install the libraries (if you use shared libraries and don't install them
> to the system locations, you need to specify their location explicitly
> at runtime with LD_LIBRARY_PATH). It does seem to work fine when you turn
> SHAREDLIBS on in the config (apart from one program which refuses to
> build due to a makefile bug which makes it still want to link against the
> static libraries), and the resulting applications end up a lot smaller as
> a result.
> 
> --
> ------- Alex Holden -------
> http://www.linuxhacker.org/
>  http://www.robogeeks.org/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####