> > 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.
Yes, I initially found the PKG_CONFIG_PATH thing surprising but, once I'd found out about it, I found that I liked it! Just don't change your mind again, ok? ;) > > 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. Yes boss :). I'll commit a fix. > > 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 Ah yes, a trap for the unwary. My bad. I imagine that would work. Would have been nice to ./configure to tell me I was a bit of a monkey there though... Is that possible with automake? This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
