|
From: | Ralf Corsepius |
Subject: | Re: Finding dependencies in lib64 or lib |
Date: | Thu, 11 Feb 2010 17:24:00 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 |
On 02/11/2010 03:51 PM, Daniel Pocock wrote:
Peter Breitenlohner wrote:On Thu, 11 Feb 2010, Daniel Pocock wrote:
Well, the LDFLAGS, CPPFLAGS, CFLAGS approach is intrinsic to autoconf/automake.I agree that this is one solution, and Ralf's suggestion about LDFLAGS is also valid of course. I didn't see any example in the documentation endorsing a particular approach,
It's just a standard use-case of autoconf/automake, which doesn't need special casing. It also is the standard use-case, how distribution packagers apply autoconf/automake.
Exactly. There is a lot of confusion about this topic around, and a lot of uncooked recipes around, seemingly stemming from people who never used multilibs and multiarched systems.and every project I've looked at seems to handle the problem in a slightly different way. Of course maybe many of them are a little broken.
These kind of config scripts are problem-zone of their own, because many of them are not multilib-ready.There is another case that we handle as well: some libs provide a -config script, e.g. apr-1-config, so you can specify
E.g. many projects *-config scripts which stem off from early gtk-config/glib-config ... unfortunately, these were not multilib ready.
The feature pkg-config adds, is it providing a systematic (though arguable) approach - But this is yet another topic.
Ralf
[Prev in Thread] | Current Thread | [Next in Thread] |