comp.lang.ada
 help / color / mirror / Atom feed
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
Subject: Re: Library file locations (was: Debian Policy for Ada, Second Edition)
Date: Mon, 20 Mar 2006 12:51:18 +0100
Date: 2006-03-20T12:51:18+01:00	[thread overview]
Message-ID: <87acbl8hc9.fsf@ludovic-brenta.org> (raw)
In-Reply-To: ghuTf.1269$Cd.1225@reader1.news.jippii.net

Tapio Kelloniemi <spam18@thack.org> writes:
>>In particular, /usr/local is, by definition, for use by the system
>>administrator, and therefore falls outside the scope of any policy
>>defined by the operating system.
>
> Why GCC then looks for headers in /usr/local/include? Because many packages
> are installed in /usr/local by sysadmins and because /usr/local/include
> is in GCC's default search path, other packages can link against 
> packages installed by admin without using absolute paths. Has anyone ever
> seen C code like:
> #include "/usr/local/include/readline/readline.h"

No but I often see:

gcc -c -I/usr/local/include foo.c

> What comes to setting ADA_PROJECT_PATH, I think it is just setting
> one more redundant environment variable. Editing a text file is much
> more elegant solution.

But you would normally set ADA_PROJECT_PATH from within a Makefile, so
your objection is weak.

>> If you want GNAT to look in some
>>particular subdirectory of /usr/local, then use ADA_PROJECT_PATH or
>>"with" the fully qualified file name of your project files.
>
> Let us think that I'm to publish my application A in source format on my
> web site. The package is built with a command like:
> gnatmake -PA
>
> If my project file contains something like:
> with "/usr/share/ada/adainclude/florist.gpr";
> with "/...";
> with "/...";
>
> Suddenly I'll get a lot of complaints that compiling my application is very
> frustrating because users must hassle with the absolute path definitions
> in my project file.

As I said, gnat-4.1 will look in /usr/share/ada/adainclude by default,
so you will not need absolute paths.  So your objection is addressed.

Secondly, even if gnat didn't look in that directory by default,
nobody could blame you for following the GNAE standard, could they?

>>So, what exactly is the problem?
>
> Easy usage of libraries, no matter whether they are installed by a
> sysadmin or a distro.

And the Debian Policy for Ada addresses just that problem.  I meant,
what is the *remaining* problem after you've read the Debian Policy
for Ada?

-- 
Ludovic Brenta.



  reply	other threads:[~2006-03-20 11:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18  1:15 Debian Policy for Ada, Second Edition Ludovic Brenta
2006-03-18 13:36 ` Pascal Obry
2006-03-18 14:39   ` Ludovic Brenta
2006-03-18 16:32     ` Pascal Obry
2006-03-18 17:13       ` Ludovic Brenta
2006-03-18 19:10         ` Pascal Obry
2006-03-18 19:49           ` Georg Bauhaus
2006-03-18 21:16       ` Tapio Kelloniemi
2006-03-19  2:04         ` Library file locations (was: Debian Policy for Ada, Second Edition) Björn Persson
2006-03-19  7:48           ` Tapio Kelloniemi
2006-03-19 13:00             ` Björn Persson
2006-03-19 15:31             ` Pascal Obry
2006-03-19 16:48               ` Björn Persson
2006-03-19 20:21               ` Tapio Kelloniemi
2006-03-19 22:24                 ` Ludovic Brenta
2006-03-20  9:07                   ` Tapio Kelloniemi
2006-03-20 11:51                     ` Ludovic Brenta [this message]
2006-03-21 20:11                       ` Tapio Kelloniemi
2006-03-21 22:30                         ` Library file locations Ludovic Brenta
2006-03-22 11:57                         ` Library file locations (was: Debian Policy for Ada, Second Edition) Georg Bauhaus
2006-03-20  6:52                 ` Pascal Obry
2006-03-20  9:10                   ` Tapio Kelloniemi
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox