Build failure with RTT master and OCL 2.3 due to log4cpp
| Submitted by Sylvain Joyeux on Fri, 2011-05-13 08:04 |
The problem is that OCL's cmake code does not find log4cpp
Two things:
* since log4cpp ships a pkg-config file, could we not just use that
instead of having a custom cmake macro ?
* it seems that the problem is that log4cpp installs only a debug
library (with a d postfix). What is the purpose of those libraries ?
(I saw them arriving in other CMake stuff from RTT as well). How can
I make it install the non-debug version / name ?
Sylvain
Build failure with RTT master and OCL 2.3 due to log4cpp
On Friday 13 May 2011 10:00:44 Sylvain Joyeux wrote:
> The problem is that OCL's cmake code does not find log4cpp
>
> Two things:
> * since log4cpp ships a pkg-config file, could we not just use that
> instead of having a custom cmake macro ?
I have no preference. But this is not causing it.
> * it seems that the problem is that log4cpp installs only a debug
> library (with a d postfix). What is the purpose of those libraries ?
> (I saw them arriving in other CMake stuff from RTT as well). How can
> I make it install the non-debug version / name ?
Oops. I thought the debug postfix would only be picked up in win32 builds. The
cmake statement needs to be wrapped with an if(WIN32) guard. I'll push that
fix.
If autoproj on maverick would be fixed, my build farm would have found this
three weeks ago. The reality is that no testing of the full toolchain
(ocl+log4cpp etc) is going on because of this.
Peter
Build failure with RTT master and OCL 2.3 due to log4cpp
On May 13, 2011, at 05:45 , Peter Soetens wrote:
> On Friday 13 May 2011 10:00:44 Sylvain Joyeux wrote:
>> The problem is that OCL's cmake code does not find log4cpp
>>
>> Two things:
>> * since log4cpp ships a pkg-config file, could we not just use that
>> instead of having a custom cmake macro ?
>
> I have no preference. But this is not causing it.
>
>> * it seems that the problem is that log4cpp installs only a debug
>> library (with a d postfix). What is the purpose of those libraries ?
>> (I saw them arriving in other CMake stuff from RTT as well). How can
>> I make it install the non-debug version / name ?
>
> Oops. I thought the debug postfix would only be picked up in win32 builds. The
> cmake statement needs to be wrapped with an if(WIN32) guard. I'll push that
> fix.
Sorry Sylvain, I fixed this a couple of weeks ago, but it was sitting on my toolchain-next branch (not toolchain). Thanks for pushing Peter.
Peter, was is your logic for advancing toolchain and master, but not stable, with this patch?
S