curl-config --version didn't output the correct version string (bug introduced in commit 0355e33), and unfortunately the test case 1022 that was supposed to check for this was broken. This change fixes the test to detect this problem and it fixes the output. Bug: http://curl.haxx.se/bug/view.cgi?id=3288727
The curl-config now features a --built-shared command line option that will output 'yes' or 'no' depending if the build process was asked to build shared library/libraries or not. It is primarily made to offer more details to the test suite to know what kind of stunts it can expect to work.
…kg-config file for libcurl, and while doing that fix he unified with curl-config.in how the supported protocols and features are extracted and used, so both those tools should now always be synced.
…tput (it already before skipped /usr/lib). /usr/lib64 is the default library directory on many 64bit systems and it's unlikely that anyone would use the path privately on systems where it's not.
tracker (https://bugzilla.redhat.com/show_bug.cgi?id=316191), I now made curl-config --features and --protocols show the correct output when built with NSS.
…ally not supporting it. It hasn't been functioning for years anyway, so this is just finally stating what already was true. And a cleanup at the same time.
--features was used
…ns what protocols that are disabled.
Here's a stab at a consolidation of the SSL detection heuristics into configure. Source files aren't changed by this patch, except for setup.h and the various config*.h files. Within the configure script, OPENSSL_ENABLED is used to determine if SSL is being used or not, and outside configure, USE_SSLEAY means the same thing; this could be even further unified some day. Now, when SSL is not detected, configure skips the various checks that are dependent on SSL, speeding up the configure process and avoiding complications with cross compiles. I also updated all the architecture- specific config files I could see, but I couldn't test them.
…-cflags is not a good thing, as recent gccs for example complain if it is /usr/include Right now, we just output "" until we think of something better.
…sible to compile libcurl stuff without any prior knowledge: cc=`curl-config --cc` cflags=`curl-config --cflags` libs=`curl-config --libs` $cc $flags $libs -o example example.c Or if you prefer, the oh-so-cool single-line version: `curl-config --cc --cflags --libs` -o example example.c
when building anything with libcurl
which libcurl itself is installed in.
that have been built-in