You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Nicholas Clark (Jira)" <lo...@logging.apache.org> on 2022/01/31 16:52:00 UTC
[jira] [Updated] (LOGCXX-551) CMake documented build option for Boost vs C++17 Implementation for shared_mutex
[ https://issues.apache.org/jira/browse/LOGCXX-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas Clark updated LOGCXX-551:
----------------------------------
Description:
There was a recent approach to detecting if boost' implementation is needed, but I feel that it is not succinct and cannot be when it comes to linker issues.
I have large applications that use shared_mutex, but require boost' implementation as not all components linked are able to use C+\+17 implementation at this time. A problem occurs during linkage when log4cxx is built using C+\+17's implementation but our other component is built using boost' implementation.
*Workaround:*
We currently can force cmake into using Boost' implementation by passing:
{code:java}
-DSTD_SHARED_MUTEX_FOUND=0{code}
This isn't a documented 'feature'. I would like a documented approach to this. If -DSTD_SHARED_MUTEX_FOUND=0 is what we should use for this feature request, then it should be documented as such. I am putting forth this issue as current usage is not documented as supported and thus I suspect it may be lost in future commits.
was:
There was a recent approach to detecting if boost' implementation is needed, but I feel that it is not succinct and cannot be when it comes to linker issues.
I have large applications that use shared_mutex, but require boost' implementation as not all components linked are able to use C++17 implementation at this time. A problem occurs during linkage when log4cxx is built using C++17's implementation but our other component is built using boost' implementation.
*Workaround:*
We currently can force cmake into using Boost' implementation by passing:
{code:java}
-DSTD_SHARED_MUTEX_FOUND=0{code}
This isn't a documented 'feature'. I would like a documented approach to this. If -DSTD_SHARED_MUTEX_FOUND=0 is what we should use for this feature request, then it should be documented as such. I am putting forth this issue as current usage is not documented as supported and thus I suspect it may be lost in future commits.
> CMake documented build option for Boost vs C++17 Implementation for shared_mutex
> --------------------------------------------------------------------------------
>
> Key: LOGCXX-551
> URL: https://issues.apache.org/jira/browse/LOGCXX-551
> Project: Log4cxx
> Issue Type: Wish
> Components: Build, Documentation
> Affects Versions: 0.12.1
> Reporter: Nicholas Clark
> Priority: Minor
>
> There was a recent approach to detecting if boost' implementation is needed, but I feel that it is not succinct and cannot be when it comes to linker issues.
> I have large applications that use shared_mutex, but require boost' implementation as not all components linked are able to use C+\+17 implementation at this time. A problem occurs during linkage when log4cxx is built using C+\+17's implementation but our other component is built using boost' implementation.
>
> *Workaround:*
> We currently can force cmake into using Boost' implementation by passing:
> {code:java}
> -DSTD_SHARED_MUTEX_FOUND=0{code}
> This isn't a documented 'feature'. I would like a documented approach to this. If -DSTD_SHARED_MUTEX_FOUND=0 is what we should use for this feature request, then it should be documented as such. I am putting forth this issue as current usage is not documented as supported and thus I suspect it may be lost in future commits.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)