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,1f44263ee326f015,start X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Path: g2news1.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!gegeweb.org!aioe.org!.POSTED!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Build / Make configuration tools and Ada medium or large projects Date: Tue, 08 Feb 2011 11:23:16 +0100 Organization: Ada @ Home Message-ID: NNTP-Posting-Host: oPrsMnjZI9WjFXCbS6E0zA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/11.01 (Win32) X-Notice: Filtered by postfilter v. 0.8.2 Xref: g2news1.google.com comp.lang.ada:16977 Date: 2011-02-08T11:23:16+01:00 List-Id: Hello, While GCC optionally supports Ada, the GNU build configurations, both on= = end user and upstream side, seems mostly C/C++ oriented (as I feel). = Anyway, honestly, I do not enjoy these, not even Makefiles which looks = most of time unreadable to me (I am even less seasoned with these), and = = the overall process is not always that much clear to me (mostly when err= or = occurs when I want to compile something for which no Windows binaries ar= e = provided). I was looking at some alternatives, and found about Waf http://en.wikipedia.org/wiki/Waf and CMake http://en.wikipedia.org/wiki/Waf Still both, while they looks nice, still seems to be C/C++ oriented. Whe= n = I read CMake as used for the KDE project was able to generate standard = Makefiles along with MSVC project files, I cannot avoid the though =E2=80= =9CMSVC = does not support Ada=E2=80=9D (as an example). What kind of tools comes with knowledge of overall available Ada compile= rs = and vendors associated project management ? Say you have an Ada project = = organized with AdaCore's GPR files, what would you use to make this = project buildable with another vendor project management facilities and = = compilers ? At least, does it miss to someones ? Or no ones bother because nobody = ever faced the case ? (if the second is the true one, this may explain w= hy = I have never seen this) I know Ada does not suffer some weird requirements typical of C and whic= h = was the first reason for the need of Makefiles to build C applications, = = but this does not cover all cases. At least some topic likes source file= = names layout, file hierarchy, search paths, ways to select set of bodies= = (when multiple are available) for a given package, linker options for = non-Ada stuffs like libraries, C files, etc, all of these cannot be hand= le = by the Ada package system alone (by the way, using pragmas for linker = options may not be that good, as I am not sure other compilers would = really understand these options the intended way). If GPR files are a kind of standard supported by other vendors and not = only GNAT, then there is nothing to search for, as everything would be = already there. But I don't believe this is so widely used, as GNAT being= = the most widely know Ada compiler, does not mean this is shared by = everyone (this may be only true for some kind of users). Some testimonies and witnesses on the topic ? -- = Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es= t pas pour = les chiens. =E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]