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: 103376,de92eb048dc3c019 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!news3.google.com!news.glorb.com!tudelft.nl!txtfeed1.tudelft.nl!feeder1.cambrium.nl!feed.tweaknews.nl!news.netcologne.de!nhp.netcologne.de!newsfeed.arcor.de!news.arcor.de!not-for-mail Date: Wed, 22 Mar 2006 12:57:18 +0100 From: Georg Bauhaus Organization: future apps GmbH User-Agent: Debian Thunderbird 1.0.2 (X11/20051002) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Library file locations (was: Debian Policy for Ada, Second Edition) References: <87acbl8hc9.fsf@ludovic-brenta.org> <36ZTf.1851$ay4.142@reader1.news.jippii.net> In-Reply-To: <36ZTf.1851$ay4.142@reader1.news.jippii.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <44213b94$0$2581$9b4e6d93@newsread2.arcor-online.net> NNTP-Posting-Date: 22 Mar 2006 12:57:08 MET NNTP-Posting-Host: 597ef6ab.newsread2.arcor-online.net X-Trace: DXC=5l54FacR?m1?0I78\m5cj:Q5U85hF6f;4jW\KbG]kaM86=9@_^g[50F7T5IO2 X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:3552 Date: 2006-03-22T12:57:08+01:00 List-Id: Tapio Kelloniemi wrote: > /usr/local should be supported automatically or at least easily. > What comes to setting ADA_PROJECT_PATH in a Makefile: As the name 'local' says (to me, at least), what is in /usr/local should be treated as local. Hence a global compiler should not at all have knowledge of, or be interest in, what is in /usr/local. > Imagine that I have installed some Ada library under /usr/local (the distro > provides a precompiled binary, but I want to enable a feature X required by > package A). Then I compile A. If the library and the package A were written in > C, I would do the following to compile A: > ./configure && make && make install > > As they are written in Ada, I do: > ./configure --with-additional-ada-project-path=/usr/local/share/ada/adainclude > > And what if the configure script does not support the above mentioned option? I do hope that use of configure etc is rare with Ada. Reason 1: Ada itself has good configuration facilities. Reason 2: Make is pretty good in steering them. Ada compilation systems tend to have project compilation management programs. Reason 4: Unlike Ada, auto* is horribly non-portable across OS toolsets, and has been shown to contribute to the problem it is supposed to solve. Georg