Re: Multiple shared libraries with a single spec

["Lucretia" <lucretia9@lycos.co.uk>]

Niklas Holsti wrote:
> Ah - when you say "shared lib", do you mean a *dynamically* linked
> library? I thought you just meant a library that is used by
> several programs or different versions of a program, but has
> different implementations for different environments.

Nope a shared library, as in dynamically linked. Hence the use of
dlopen and dlsym in the OP ;-D

> Sorry for my misunderstanding. I don't have any experience with
> making dynamically linked libraries.

No problems. It took a while to get sorted, but it can be done,
although GNAT really makes it difficult.

> In my case, the choice of versions influences many parts of the
> program, not just the libraries but also their client packages, so
> linking the libraries dynamically would not make sense.
>
> > Do you dump the ali and shared lib to a different directory?
>
> It may not be relevant to your problem, as I misunderstood your
> aims, but for this program I never have the .adb in the same
> directory as the .ali and .o.

Ok. I currently build in the directory with the source, I should change
this so that the objects and ali's go somewhere else.

Luke.