From: Robert Ramey (ramey_at_[hidden])
Date: 2004-12-26 12:11:25
After some investigation, I've concluded that the addition of auto-link
macros doesn't break normal static library builds. So that's OK. I'm still
investigating the other questions.
Robert Ramey wrote:
> OK -
> a) The document re:auto-link indicates that not all platforms support
> it. That leaves me wondering what happens when the macros are
> included in the library source code an its compiiled? Is there an
> error message. Does everything work with the same as w/o auto-linking
> b) I notice that Comeau doesn't show up in the test matrix. This
> made me wonder if the configuration for the comeau compiler has been
> updated to consider the auto-link idea. In fact, since Commeau is a
> "pre-compiler" its not even clear to me that can be fit in.
> c) When I build with comeau. The auto-link macros seem to be
> This makes me wonder if the config files ro comeau need to be altered
> take this into account.
> d) The above makes me wonder if comeau config files have not been
> kept up.
> So my question is:
> Have comeau config files been kept up with changes required to support
> auto-link. If so, why is not comeau appearing in the test matrix?
> Robert Ramey
> David Abrahams wrote:
>> Robert Ramey wrote:
>>> I've made source changes to accommodate Comeau.
>>> Now even static libraries fail to compile on with this compiler.
>>> Is this the intention or am I missing something.
>> There's so little context in this message that it's almost impossible
>> to imagine anybody giving a useful answer. Whose intention? Which
>> libraries fail to compile? What kind of failures do you see?
>> I'm sure you understand that nobody at Boost intends for all library
>> compilations to fail, so it's hard to even understand your question.
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk