From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a37:7086:: with SMTP id l128mr15826500qkc.172.1592861262032;
        Mon, 22 Jun 2020 14:27:42 -0700 (PDT)
X-Received: by 2002:a9d:24a3:: with SMTP id z32mr5397894ota.342.1592861261751;
 Mon, 22 Jun 2020 14:27:41 -0700 (PDT)
Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 22 Jun 2020 14:27:41 -0700 (PDT)
In-Reply-To: <rcr73s$1iq4$1@gioia.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=216.121.185.139; posting-account=ENgozAkAAACH-stq5yXctoDQeZQP2E6J
NNTP-Posting-Host: 216.121.185.139
References: <3f234cce-c49f-40a4-83a4-f0c9860d8abfo@googlegroups.com>
 <rcqmr4$1rc9$1@gioia.aioe.org> <98843f83-9907-4bd4-9600-4bc67e41f883o@googlegroups.com>
 <rcr32c$1osc$1@gioia.aioe.org> <ly5zbihlvy.fsf@pushface.org> <rcr73s$1iq4$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0c79ea0b-bf56-4690-a9a6-fcc6a5c0f49co@googlegroups.com>
Subject: Re: How to supply O/S linker arguments with gprbuild?
From: Warren <ve3wwg@gmail.com>
Injection-Date: Mon, 22 Jun 2020 21:27:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader01.eternal-september.org comp.lang.ada:59169
List-Id: <comp.lang.ada>

On Monday, 22 June 2020 17:16:50 UTC-4, Dmitry A. Kazakov  wrote:
> On 22/06/2020 22:43, Simon Wright wrote:
> > "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> >=20
> >> Another idea to consider would be to ditch makefiles. gprbuild does
> >> everything makefiles do and better and more.
> >=20
> > Almost everything! except determining which OS you're running under, or
> > building project documentation, or ...
>=20
> Are you sure that make has OS macro defined? [It would be great to have=
=20
> host OS/architecture + target OS/architecture attributes in gpr. I do=20
> not understand why gpruild still does not have them.]
>=20
> Isn't there the package Documentation in grpbuild? [I must admit I never=
=20
> used it because I believe documentation must be written, not built.]
>=20
> If you rather mean project cross reference GPS does the job to me.
>=20
> --=20
> Regards,
> Dmitry A. Kazakov
> http://www.dmitry-kazakov.de

I don't need the OS defined in make. All I need is agree on a few conventio=
ns such as PREFIX and define some easily customized macros at the top of th=
e Make file.=20

Even knowing that your OS is Linux, doesn't really help. While there are th=
e usual standard places for libraries, there is no guarantee that you'll be=
 linking with those directories. On an older CentOS for example, the newer =
updates are often installed in custom places like /opt because the older li=
braries must be maintained for the rest of the system. Shared libraries can=
 be quite the nightmare with the inter-dependencies and versions (same deal=
 as the Windows DLL hell).