AMDG On 03/11/2012 09:34 PM, Emil Dotchevski wrote:
It appears that both the <threadapi> and <python-debugging> properties cause the same problem. Currently, my only workaround is to delete all mentioning of <threadapi> and <python-debugging> from the Boost distribution Jamfiles, which obviously is not ideal.
I think that the problem is due to some of my own targets being seen twice in the same build environment: once before and once after Boost Thread and Boost Python get defined, leading to the ones seen before to be missing the default values of <threadapi> and <python-debugging>.
Does this seem plausible? Is there a solution to this problem?
I'm sure you're correct. The best solution right now is to force boost thread to be loaded earlier with use-project. In the long term, I'd like to re-do property handling to make this a non-issue, but that requires major changes. In Christ, Steven Watanabe