[
https://issues.apache.org/jira/browse/MESOS-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073845#comment-14073845
]
Craig Hansen-Sturm edited comment on MESOS-1626 at 7/24/14 11:43 PM:
---------------------------------------------------------------------
Timothy, I have a question for you: I'm hearing that our dependency checker
strips out headers for libs containing types which are unreferenced in mainline
code.
Given this, what is the proper way to introduce (in this case, boost headers)
back prior to introducing new dependencies into mainline code ? e.g., adding
the declarations, wrapping them in stout, and, only then, using the
declarations.
I'm assuming a patch for boost is not the right way to do this, but am unsure
what the staging process is.
Please advise ! thanks.
was (Author: craig-mesos):
Timothy, I have a question for you: I'm hearing that our dependency checker
strips out headers for libs containing types which are unreferenced in the code.
Given this, what is the proper way to introduce (in this case, boost headers)
back prior to introducing the dependency in mainline code ? I'm assuming a
patch is not the right way to do this, but am unsure.
Please advise.
> Add support for C++11 (+Boost) <atomic> to stout
> ------------------------------------------------
>
> Key: MESOS-1626
> URL: https://issues.apache.org/jira/browse/MESOS-1626
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
> Reporter: Craig Hansen-Sturm
> Assignee: Craig Hansen-Sturm
> Priority: Minor
> Attachments: boost-1.53.0.patch
>
>
> Integrate c++11/atomic into libprocess/stout following the pattern introduced
> by c++11/memory and c++11/lambda. The primary difference in this case, is
> that tr1 did not include support for <atomic>, this has to come from
> boost/atomic which was introduced in v1.53. This task will include a patch
> to update boost as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
