From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,170b136bef612224 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII X-Received: by 10.224.88.200 with SMTP id b8mr28093207qam.8.1366923614518; Thu, 25 Apr 2013 14:00:14 -0700 (PDT) X-Received: by 10.49.86.200 with SMTP id r8mr3781410qez.25.1366923614494; Thu, 25 Apr 2013 14:00:14 -0700 (PDT) Path: ef9ni16888qab.0!nntp.google.com!gp5no6972974qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 25 Apr 2013 14:00:14 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=206.53.78.59; posting-account=ShYTIAoAAABytvcS76ZrG9GdaV-nXYKy NNTP-Posting-Host: 206.53.78.59 References: <8f5e2358-05ab-4b0f-82be-b2f2d7438765@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <90c9e44e-3925-463d-85c7-2fef06ab1c4e@googlegroups.com> Subject: Re: Specifying a target in a GPRBuild project file? From: sbelmont700@gmail.com Injection-Date: Thu, 25 Apr 2013 21:00:14 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2013-04-25T14:00:14-07:00 List-Id: On Thursday, April 25, 2013 5:01:32 AM UTC-4, Hibou57 (Yannick Duch=EAne) w= rote: >=20 > Finally, that's not loosing anything: the `--target` option is not safe a= t =20 >=20 > all, using the `--config` option is better. The reason is that with =20 >=20 > `--config` you are sure to get what you expect or else an error. With =20 >=20 > `--target`, if it does not find the compiler with the default =20 >=20 > configuration, you may have an `aut.cgpr` for a different target than the= =20 >=20 > one specified for the option. >=20 While I generally agree that using --config is better than --target (we hav= e 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 sing= le gpr should be able to conditionally control the source directories (et a= l) based on what the target will be. =20 Its senseless that I have to do something like this: gprbuild --config=3Dvxworks.cgpr --Xtarget=3Dvxworks project.gpr when 1.9.10.1 clearly states (under the 'configuration-general heading) tha= t 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 gue= ss, but like you said, things should work how they are documented. -sb