Re: GNAT, shared libraries, building in different directories...madness!

["Philippe Bertin" <philippe.bertin@telenet.be>]

While we are at it, is there somewhere a good reference document on the
different .gpr options ? As in GPS, one can specify options in the IDE,
and see them reflected in GPS' created .gpr file. But then again, I was
not aware of gps file's features like

<snip from Ludovic Brenta's post>
project Build_Adael is
   Compiler := External ("COMPILER", "gnat");
   Target   := External ("TARGET", "linux");
   Build    := External ("BUILD", "release");
 ...
end Build_Adael;
</snip>

that can be passed along to gnatmake using the -X option. Are there
more of such 'hidden' (?) options/features ?

Furthermore, there are 2 environment variables (ADA_INCLUDE_PATH,
ADA_OBJECTS_PATH)  that can be set for gnatmake's sake; setting these
do not necessitate passing to gnatmake the options for gcc and gnatbind
(in the case of a project having to use sources/object files in other
directories). As an example (supposed one wants to dynamically link
against the system's available gtkada library)

ADA_INCLUDE_PATH=/usr/local/gtk/include/gtkada
ADA_OBJECTS_PATH=/usr/local/gtk/include/gtkada
gnatmake window1.adb -largs `gtkada-config --libs`

which ends up in a call to gnatlink equivalent to :
gnatlink /home/papa/TestProjecten/GladeGUI/src/window1.ali
`gtkada-config --libs`

But then again, I have not found any such environment variable for
gnatlink's sake. Is there any such variable that can be set to avoid
this "-largs `gtkada-config --libs`"?

Thanks,

PhB