Pascal Obry <pascal@obry.net> wrote:
>Ludovic Brenta a écrit :
>
>> I am not aware of a GNAT default.  What is the default? And why does
>> it not follow the GNAE?
>
>The scheme is something like:
>
>/opt/GNAT/<ver>
>  /bin                 <- binaries there
>  /lib/gnat/           <- project files there (GNAT looks there)
>  /lib/gnat/<project>  <- if needed sub-project files
>  /lib/<project>       <- .o .ali .a .so for <project>
>  /lib                 <- sym links to .a and .so above
>  /include/<project>   <- .ads/.adb for <project>

GNAT people seemingly haven't read FHS. This is what it says about the
include directory:
"This  is  where all of the system's general-use include files for the C
programming language should be placed."

Non-C languages generally use lib, like Python and Ruby. Even GNAT
installs its library's .adb and .ads files to lib/gcc/*/*/adainclude even 
though libstdc++ headers go to /usr/include/c++. I'm not saying that GNAT 
people made a wrong decision when they choose include, but at least they 
should be consistent.

I would like to raise the question publicly: where Ada-folks would like to put 
their .adb and .ads files? Well, perhaps this is redundant, since most likely 
people will follow the path set up by GNAT.. I'm very glad that after all 
these years GNAT developers have recognised that there must be a general way 
to link against external libraries, whereas this feature has always been 
present for C and C++ (at least in the GNU system).

-- 
Tapio