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 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.180.20.105 with SMTP id m9mr2892712wie.5.1367665494077; Sat, 04 May 2013 04:04:54 -0700 (PDT) Path: hg5ni66815wib.1!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!194.109.133.87.MISMATCH!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!backlog1.nntp.dca.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.news.ucla.edu!nrc-news.nrc.ca!News.Dal.Ca!news.litech.org!news.etla.org!aioe.org!.POSTED!not-for-mail From: Pascal Obry Newsgroups: comp.lang.ada Subject: Re: Specifying a target in a GPRBuild project file? Date: Fri, 26 Apr 2013 18:09:37 +0200 Organization: Aioe.org NNTP Server Message-ID: <517AA6C1.7050508@obry.net> References: <8f5e2358-05ab-4b0f-82be-b2f2d7438765@googlegroups.com> <51796066.5060906@obry.net> <1jpdzc49i9m1w.12yp9l8whf5lk$.dlg@40tude.net> NNTP-Posting-Host: KMOsx35cI/C1UVZUrQuUkg.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr-FR; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0 X-Notice: Filtered by postfilter v. 0.8.2 X-Original-Bytes: 2501 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: 2013-04-26T18:09:37+02:00 List-Id: Le 25/04/2013 21:02, Dmitry A. Kazakov a �crit : > For this purpose I am using a scenario variable that controls Compiler, > Linker etc packages. It also manipulates Source_Dirs because different > targets have some source files different (I don't want to use > preprocessor). No scenario variable won't help calling the right tool chain. For example if you compile a Win32 version of a project from Linux the proper winres tool will be called: $ gprbuild --target=i686-pc-mingw32 prj.gpr And if one of the language is winres then at some point a call to: $ i686-pc-mingw32-winres ... will be made. There is no way to achieve that with scenario variables which are useful to select proper sources and naming scheme. It is also used to pass the proper libraries. In fact most of the time I'm using: $ gprbuild --target=i686-pc-mingw32 -XTARGET=Windows prj.gpr That is, I teach gprbuild about the cross environment using the proper triplet name and the project file circuitry about the variant I'm building. Most of the time the TARGET project variable is UNIX, Darwin or Windows. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B