Re: gprbuild fun

[Simon Wright <simon@pushface.org>]

Brian Drummond <brian@shapes.demon.co.uk> writes:

> On Sun, 28 Jun 2015 18:28:13 +0100, Simon Wright wrote:
>
>> I have a mixed-language GPR like
>> 
>>    project build is
>>       for languages use ("ada", "c");
>>       for source_files use ("a.adb", "c.c");
>>       package ide is
>>          for compiler_command ("ada") use "gnatmake";
>>       end ide;
>>    end build;
>
>> and, if I have the native gcc and arm-eabi-gcc present in the PATH,
>> gprbuild chooses to use the native gcc for the Ada part and arm-eabi-gcc
>> for the C part!
>> 
>> Fix: delete the compiler_command line.
>
> Presumably, ... editing it to arm-eabi-gnatmake would also work?

But I wanted the native version! --target=x86_64-apple-darwin13. Which
I've never had to say before.

As you suggest, for compiler_command ("ada") use "arm-eabi-gnatmake"
works, in the sense of selecting a consistent set of tools.

But the thing is, if you specify compiler_command, gprconfig is invoked
with e.g.

   gprconfig --batch -o /Users/simon/tmp/gprbuild-problem/auto.cgpr
   --target=all --config=c,, --config=ada,,,,gnatmake

but if you don't it's invoked with

   gprconfig --batch -o /Users/simon/tmp/gprbuild-problem/auto.cgpr
   --target=x86_64-darwin --config=c,, --config=ada,,

So where did it get --target=all from?! (and come to that where did
x86_64-darwin come from? x86_64-apple-darwin I would have understood)