On Tue, 22 Apr 2014, Dilyan Palauzov wrote:

> with this patch applied on top of git/master, running "./configure
> --with-nghttp2" finds libnghttp2.

Great, I pushed it to git just now! Thanks for testing and confirming.

> Howerver, running just "./configure" does not activate libnghttp2.

That's made on purpose. Both nghttp2 and the http2 code in libcurl are still
moving targets and I prefer it to be an active decision to try that out rather
than a wider default check until things stabelizes more. Like a fixed nghttp2
API and a released http2 spec for example.

> For the person configuring curl, it shall be clear by looking from
> "./configure --help" which options are unnecessary to achieve certain
> configuration, and which are needed to tweak something.

> This practice shall be applied consistently over all options: Is with
> "./configure" --enable-debug or --disable-debug active, and so on.

That's not a bad thought, but is it really feasable? ./configure --help is a
whopping 244 lines already. I count 71 --with* and --enable* lines. The amount
of information there drowns even experienced hackers. I'm far from convinced
that adding 'default' on 70 something places will help...

I consider the final summary output far more helpful actually!

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html