Don't install config.h or include it in headers

[GoogleCodeExporter]

config.h is an artefact of the GNU autotools and is dependent on the local 
build environment. It is not meant to be distributed to other systems, nor 
installed as headers, since it would then conflict with other generated 
config.h files in projects that include these headers, because they define the 
same macros.

For more details, see:
 - http://stackoverflow.com/questions/1810216/autoconf-where-does-config-h-go
 - http://inaugust.com/post/68
 - http://gnu-autoconf.7623.n7.nabble.com/make-install-config-h-td18986.html

I have provided a patch which works for the non-windows build. For the windows 
build, you could conditionally copy config.win32.h to config.h if you detect a 
windows system, then leave it out during the install.

Unfortunately this also means that projects that use curlpp must provide a 
config.h themselves, perhaps using GNU autotools, but this is The Correct Thing 
To Do.

Original issue reported on code.google.com by infini...@pwned.gg on 21 Sep 2013 at 11:06

Attachments:

• dont-install-config-h.patch

[GoogleCodeExporter]

Actually, that isn't so bad. The only config.h macro that the headers make use 
of is HAVE_BOOST, so users only need to worry about defining this rather than 
entire GNU autotools functionality.

Original comment by infini...@pwned.gg on 21 Sep 2013 at 11:27