Re: GNAT library directory - how to detect it at build time?

[Simon Wright <simon@pushface.org>]

Maciej Sobczak <see.my.homepage@gmail.com> writes:

> Hi,
>
> I have two Linux systems. On one GNAT keeps its library files in the
> following directory:
>
>    /usr/lib/gcc/i486-linux-gnu/4.4
>
> but on the other the directory is:
>
>    /usr/lib/gcc/x86_64-linux-gnu/4.6
>
> Normally I do not need to name these directories during compilation
> and linking, because GNAT is smart enough to use them when
> needed. Except for files that are directly in these directories and
> can that be needed for linking. GNAT is not smart enough to find these
> files automatically and project files have to be carefully crafted to
> work around that.
>
> Is there a way to obtain these paths in the automatic way (say, via
> standard GPR variables or something like that) or to abstract them
> away with a link that is perhaps installed by GNAT always in the same
> place but that I have not yet discovered?

Not sure these will help ...

$ gnatgcc --print-libgcc-file-name
/opt/gcc-4.7.0/lib/gcc/x86_64-apple-darwin11/4.7.0/libgcc.a

or

$ gnatgcc --print-file-name=libgcc.a
/opt/gcc-4.7.0/lib/gcc/x86_64-apple-darwin11/4.7.0/libgcc.a

or the surprising

$ gnatgcc --print-file-name=adalib/libgnat.a
/opt/gcc-4.7.0/lib/gcc/x86_64-apple-darwin11/4.7.0/adalib/libgnat.a