Ben Reser asked me in the "[RFC] Build System Documentation thread"
about the gtest example:
"
> - mv $GTEST gtest
> + mv $GTEST libgtest
> + echo "Gtest has been installed, please note:"
> + echo "autogen.sh will issue spurious header warnings."
> + echo "./configure --enable-gtest will issue repeated spurious
warnings
> that"
> + echo "the option --enable-gtest is not recognsed."
Why is that? I haven't really been following the gtest work that much
but the spurious warnings issue seems like an issue in what you did
rather than something you should be adding documentation around."
The header issue:
autogen.sh complains with this error message unless the headers get
added to the private includes in build.conf at line 37, where
gen-make.py picks it up, but if the optional gtest package is not
around, it crashes the compile.
./configure warnings:
Bug report has been filed now.
