Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

2017-04-29 Thread li...@lazygranch.com
On the other hand, the current git pull has fixed the LOG4CPP problem I had with opensuse 42.2. http://gnuradio.4.n7.nabble.com/fail-tests-for-qa-cpp-py-binding-qa-cpp-py-binding-set-qa-ctrlport-probes-td63291.html It now works for both the local library build of log4cpp and the standard distrib

Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

2017-04-29 Thread Michael Dickens
Ah; thanks Bastian. I sort of remembered that something was committed that updated the use of log4cpp info. That's good. The downside is that this is not part of the current GR release, so most users won't get its benefits for a while longer -- until the next release. In MacPorts, folks can install

Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

2017-04-28 Thread Bastian Bloessl
Hi, are you talking about building in-tree modules or OOTs? On 04/28/2017 11:13 PM, Michael Dickens wrote: > Hi Eugene - What you write looks to be true about the current GR > codebase. Bastian Bloessl has a commit that adds in LOG4CPP_INCLUDE_DIR > & related to those in-tree areas that need it (

Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

2017-04-28 Thread Michael Dickens
Hi Eugene - What you write looks to be true about the current GR codebase. Bastian Bloessl has a commit that adds in LOG4CPP_INCLUDE_DIR & related to those in-tree areas that need it (branch "ugly_cmake"): < https://github.com/bastibl/gnuradio/commit/16d8e8cb9bd658991dabbc253c74850248b80f83 >. I d

[Discuss-gnuradio] CMake error related to log4cpp in non-standard location

2017-04-28 Thread Eugene Grayver
The current GR CMakeFile(s) apparently do not add the include path LOG4CPP_INCLUDE_DIR to the compile. Can't build w/ log4cpp in non-standard location. Eugene Grayver, Ph.D. Aerospace Corp., Sr. Eng. Spec. Tel: 310.336.1274 __