Re: Multiple shared libraries with a single spec

[Niklas Holsti <nobody@nowhere.fi>]

Lucretia wrote:
> Niklas Holsti wrote:
> 
>>I'm working on an Ada program that has different versions, as in
>>your example. I put the different versions of the package bodies
>>(and specifications, too, for some packages) in different
>>source-code directories, as you do. To build a specific version of
>>the program, I list the source-code directories for the desired
>>version in ADA_INCLUDE_PATH (and also in ADA_OBJECTS_PATH, but I
>>think this is unnecessary for me) and then run "gnatmake" in a
>>directory dedicated to this version. The .ali and .o files and the
>>executable go in this version-specific directory. I don't use
>>symlinks, just ADA_INCLUDE_PATH.
> 
> 
> The problem i've found is, if the .adb file is in the same directory as
> the .ali, .o and the shared lib, the source code will be linked
> directly into the final executable. The executable still requires the
> shared lib, but it doesn't actually use it. How do you get around this?

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.

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

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.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .