Re: Multiple shared libraries with a single spec

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

Stephen Leake wrote:
> What I meant was 'using file system symbolic links' is compiler
> independent. My option of using GNAT project files is not compiler
> independent.

Oh. Well, the symbolic links are only in use to get the thing working,
nothing more.

> Hmm. Maybe I misread what you wrote, and you didn't mean 'file system
> symbolic links'.
>
> > But you should be able to do this on Windows,
>
> Windows does not support file system symbolic links.

Well, yeah. But I'm working on Linux so I'm not too bothered about
getting a test program working on Windows.

> > Hmmm, haven't used project files yet.
>
> They are very nice. For example, they make it easy to specify compiler
> options on a per-file basis (which I use to work around compiler bugs
> :).

I'll look into it. Can they be used for mixed language programming? I'm
using makefiles for wxAda a the moment.

> > I ask about this, because I'm generating 2 libs, each have slightly
> > different ALI's and I was wondering whether this way would cause
> > problems in the future?
>
> Of course it can cause problems. But using per-target build
> directories, and using project files, can solve those problems.

I had another look at the ALI's and the differences were in the numbers
(hash values, I think).

Thanks,
Luke.