Steven Shaw <[EMAIL PROTECTED]> wrote: > ./configure no longer complains when it can't find cppunit. Only make fails > later when it cannot link. > > The problem is that previously I was able to use: > > PKG_CONFIG_PATH=~/local/cppunit-1.11.6/lib/pkgconfig:$PKG_CONFIG_PATH > > to configure cppunit-1.11.6. > > I have discovered that using the older cppunit-config mechanism still > works. i.e. > > PATH=~/local/cppunit-1.11.6/bin:$PATH
IMHO, this is better. People are used to the requirement of having such tools in their PATH. Having to set PKG_CONFIG_PATH is more surprising. > I liked the new pkg-config mechanism although it did require cppunit-1.11.6 > (as even cppunit-1.11.4 did not contain the cppunit.pc file). So perhaps > this change allows again the use of earlier versions of cppunit. However, > it need to be documented in one of the READMEs as to how to configure it. > i.e. that providing PATH to cpp-config is needed. Thanks for the feedback. Would you like to provide a patch for README-dev? That would help ensure it is "right" (since you're testing the procedure) and that it gets done sooner rather than later. > Note that using ./configure --with-cppunit-prefix=~/local/cppunit-1.11.6 > does not work. Same link error. How about if you use $HOME in place of '~'? ./configure --with-cppunit-prefix=$HOME/local/cppunit-1.11.6
