Re: Specifying a target in a GPRBuild project file?

[sbelmont700@gmail.com]

On Thursday, April 25, 2013 5:01:32 AM UTC-4, Hibou57 (Yannick Duchêne) wrote:
> 
> Finally, that's not loosing anything: the `--target` option is not safe at  
> 
> all, using the `--config` option is better. The reason is that with  
> 
> `--config` you are sure to get what you expect or else an error. With  
> 
> `--target`, if it does not find the compiler with the default  
> 
> configuration, you may have an `aut.cgpr` for a different target than the  
> 
> one specified for the option.
> 

While I generally agree that using --config is better than --target (we have had situations where installation of a new compiler suddenly becomes the 'default' based on the path order), the fact is that either way there is a 'target' variable defined in the .cgpr, and it ought to be available in the gpr file as project'target.  There are plenty of situations where one single gpr should be able to conditionally control the source directories (et al) based on what the target will be.  

Its senseless that I have to do something like this:

gprbuild --config=vxworks.cgpr --Xtarget=vxworks project.gpr

when 1.9.10.1 clearly states (under the 'configuration-general heading) that the target attribute "is the name of the target platform", and not always a null.  One extra command line argument isn't the end of the world, I guess, but like you said, things should work how they are documented.

-sb