Re: SOLVED: Debian Etch GCC GNAT 4.1 / Aonix ADT Eclipse Plugin

["Tom Grosman" <grosman@aonix.fr>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]

"Jeffrey Creem" <jeff@thecreems.com> a �crit dans le message de news: 
8roef4-v41.ln1@newserver.thecreems.com...
> Pieter Thysebaert wrote:
>> On Mon, 16 Apr 2007 11:33:37 +0200, Pieter Thysebaert wrote:
>>
>>> Hello,
>>>
>>> I'm on Debian GNU/Linux Etch and have installed GCC 4.1 along with the
>>> corresponding GNAT packages.
>>>
>>> I also have Eclipse 3.2 installed and downloaded (through Eclipse 
>>> Software
>>> Updates) the Aonix ADT plugin.
>>>
>>> My problem is that the ADT does not pick up Etch's GCC GNAT 4.1 
>>> toolchain
>>> (when selecting GNAT Linux Toolchain), no matter what directory I feed 
>>> it
>>> (I naively thought that setting the toolchain path to /usr/bin would do
>>> the trick).
>>>
>>
>>
>>
>> Well, I have "solved" my problem. It turns out that specifying "/usr" as
>> the toolchain path (instead of /usr/bin) does the trick...(i.e. makesd
>> Ao Aonix ADT pick up and recognize the GNAT toolchain).
>>
>> Pieter
>>
>>
>>
>
> Actually that is a good tip and makes sense. The way the plugin works, it 
> needs to find more than just the compiler and tools - it needs libraries, 
> specs, etc.
>

As I explained to Pieter, In order for AonixADT to recognize a gnat 
toolchain, The "toolchain directory" that is specified should contain the 
gnat bin subdirectory (gnat executables are located here) to which you 
should have execution permission. AonixADT then checks within the gnat bin 
directory for the presence of the executable file "gnatmake" to determine if 
you have specified a valid toolchain location. So far, this seems to work no 
matter the O/S nor compilation environment (gnuada, GNATPRO).

-Tom