Re: Specifying a target in a GPRBuild project file?

[Stephen Leake <stephen_leake@stephe-leake.org>]

"Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr> writes:

> Le Fri, 26 Apr 2013 11:54:26 +0200, Stephen Leake
> <stephen_leake@stephe-leake.org> a écrit:
>
>> Pascal Obry <pascal@obry.net> writes:
>>
>>> Le 25/04/2013 11:01, Yannick Duchêne (Hibou57) a écrit :
>>>> The `--target` option should only be used with explicit invocations of
>>>> GPRConfig, not with GPRBuild.
>>>
>>> I fully disagree. I'm building many cross tools and always using
>>> gprbuild --target=xyz. This is the way it should work, and if not
>>> probably a bug to report.
>>
>> +1
>>
>> note that gprbuild will invoke gprconfig if necessary; gprbuild is the
>> only tool a user needs to invoke directly.
>>
>
> GPRBuild invokes GPRConfig, without user interaction and
> acknowledgement from the user. If there are multiple compilers on the
> $PATH`, the choice GPRConfig made may not be good. 

The user sets PATH, so that's your user input. I reset PATH for each
project, so there is only one Ada compiler visible.

> Also, by default
> GPRBuild invokes GPRConfig each times, 

Not with the correct options:

gprbuild -p --autoconf=obj/auto.cgpr --target=x86-windows -P opentoken.gpr  wisi-generate

> and if something changed in the $PATH` or in the installed compilers,
> the configuration file may change and not for a good one.

Sure, if you change things, things change! you must have complete
control of the compilation environment. That's what makefiles are for.

> Or else a `--target` option if there is a matching `<target>.cgpr` and
> it is found by GPRBuild, but this one is just half deterministic, as
> if it don't find a `<target>.cgpr`, it won't complain and will invoke
> GPRConfig.

I agree that's a bug.

-- 
-- Stephe