configure.ac: Use CPPFLAGS, not CFLAGS for our include directives.
commite37a22f0727187654fc64fa1e3d8fb5594c7101c
authorPeter Clifton <peter@clifton-electronics.co.uk>
Thu, 3 Jan 2013 02:04:25 +0000 (3 02:04 +0000)
committerPeter Clifton <peter@clifton-electronics.co.uk>
Thu, 3 Jan 2013 02:50:15 +0000 (3 02:50 +0000)
treead1f8d9e5e01a36e4eb34f7dc7d4de978cfb7f0b
parent3b249ec65aeba349f2a71ec9025e66153755057f
configure.ac: Use CPPFLAGS, not CFLAGS for our include directives.

We were previously using CFLAGS for adding pre-processor includes, where
these should really end up in the CPPFLAGS variable. Confusingly, their
constituents tend to come from variables set by autoconf / pkgconfig
expansions in the form of LIBNAME_CFLAGS.

Doing this allows the user to easily override CFLAGS at build time without
needing to replicate the enture include path list.
configure.ac