[ 
https://issues.apache.org/jira/browse/LOGCXX-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462427#comment-17462427
 ] 

Tobias Frost commented on LOGCXX-544:
-------------------------------------

Yeah, PR #76 will help.

For the build failure, here is the Debian bug for one of the build failures: 
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001881]

The maintainer applied this patch to fix it: 
[https://paste.debian.net/hidden/baec7867/]

I did not find time to analyze whats the reason (it might be also a specific 
issue in the project using the library)

 

Cheers,

tobi

> Please embedd library version in a header
> -----------------------------------------
>
>                 Key: LOGCXX-544
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-544
>             Project: Log4cxx
>          Issue Type: Wish
>            Reporter: Tobias Frost
>            Priority: Minor
>             Fix For: 0.13.0
>
>
> I'm currently preparing the library transition in Debian, and there are 
> packages that will fail to build with version 0.12 due to the changes in API.
> While eventually all packages will use 0.12, during the transtion to the new 
> library it would be useful to be able to create patches that will allow that 
> the packages compile for the old version as well as for the new version. For 
> that it would be useful if in some header the version is available as 
> defines, to allow conditional compilations.
> (I'll try to come up with an patch, but won't be able to work right away on 
> it)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to