Hello,
here is two patches (one for log4cpp and one for orocos-ocl) to fix the
build of log4cpp in debug mode on win32. Linking orocos-ocl (debug) with
log4cpp (release) lead to segmentation fault on win32.
Philippe
| Attachment | Size |
|---|---|
| 0001-win32-fix-debug-build.patch | 1.25 KB |
| 0003-win32-fix-linking-with-log4cpp-in-debug-mode.patch | 2.14 KB |
[patch] fix win32 debug build with log4cpp
On Monday 18 April 2011 16:52:52 Philippe Hamelin wrote:
> Hello,
>
> here is two patches (one for log4cpp and one for orocos-ocl) to fix the
> build of log4cpp in debug mode on win32. Linking orocos-ocl (debug) with
> log4cpp (release) lead to segmentation fault on win32.
>
> Philippe
Thanks. pushed to toolchain-2.3
Peter
Log4cpp
Hi,
the orocos developers team maintains a fork of log4cpp. As, its a piece of
code that some other projects use. For example in debian:
http://qa.debian.org/popcon.php?package=log4cpp
and:
$apt-cache rdepends liblog4cpp5
liblog4cpp5
Reverse Depends:
libxmltooling5
sslsniff
libshibsp5
libapache2-mod-shib2
libpion-net-plugins
libpion-net-dev
libpion-net-4.0
libpion-common-4.0
opensaml2-tools
libsaml7
liblog4cpp5-dev
$apt-cache rdepends liblog4cpp5-dev
liblog4cpp5-dev
Reverse Depends:
libxmltooling-dev
So, thinking about to create debian packages of orocos-toolchain, could be
possible to rename the orocos fork to avoid collisions?
Thanks in advance,