From: Benjamin Kosnik (bkoz_at_[hidden])
Date: 2007-01-24 10:24:59
> I don't follow, how? A single
> #ifdef _REENTRANT
> in sources or headers of any given library is enough to break ABI between MT and ST
> version. I'm not aware of any automated way to check for that.
For your example of shared_ptr, you could use doxygen's collaboration
graphs to see which libs include shared_ptr includes. It's not
automated, but it's quite helpful.
I believe it also lets you track macros like BOOST_HAS_THREADS, which
seems to be how regex and others are marking up the sources for
> The problem I see is outlined above -- you don't know which libs are different between MT
> and ST builds.
It is my contention that the boost build system should definitively know
this, at least for the boost libs.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk