[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] [PATCH] detect openssl via pkg-config if it's available

From: Micah Cowan
Subject: Re: [Bug-wget] [PATCH] detect openssl via pkg-config if it's available
Date: Wed, 08 Aug 2012 11:54:54 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1

> On Thursday 24 May 2012 17:14:30 Mike Frysinger wrote:
>> On Thursday 24 May 2012 16:31:04 Giuseppe Scrivano wrote:
>>> Mike Frysinger <address@hidden> writes:
>>>> Newer versions of openssl ship with pkg-config files, so if we can
>>>> detect it via those, do so.  If that fails, fall back to the classic
>>>> method.
>>> thanks for your contribution.  It seems like a big change in the way
>>> configure will work.  I think that if we want to use pkg-config then we
>>> should use it for any external library involved, not just openssl.
>> zlib, pcre, uuid, and gnutls can be updated to search pkg-config, but
>> gcrypt and gpg-error cannot because the upstream there is being
>> pig-headed


>> lemme know which way you want to go, and i can send out an update that also
>> checks for zlib/pcre/uuid/gnutls via pkg-config.

I'll take this opportunity to point out that I had ─░lim (our GSoC
student, who has been working on support for metalink, and multiple
connections for download of a single resource) use pkg-config to detect
the libmetalink library. I believe his first iteration of support in
configure.ac had used other means to do libmetalink (gnulib's
facilities, IIRC), which we could fall back to if pkg-config isn't desired.

Personally, I favor using pkg-config where possible, particularly since
some packages sometimes need other libraries to be involved too, and
pkg-config can just tell you the full stack of -lfoo -lbar, and
-I/includes/here and -I/includes/there, without hassling the user to
specify all that themselves. libmetalink, for instance, also needs
-lxml, I believe.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]