On 02/11/2010 03:51 PM, Daniel Pocock wrote:
Peter Breitenlohner wrote:
On Thu, 11 Feb 2010, Daniel Pocock wrote:
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,
Well, the LDFLAGS, CPPFLAGS, CFLAGS approach is intrinsic to
autoconf/automake.
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.
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.
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.
There is another case that we handle as well: some libs provide a
-config script, e.g. apr-1-config, so you can specify
These kind of config scripts are problem-zone of their own, because many
of them are not multilib-ready.
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
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
