Some thoughts on DLL with runtime-link static

Repeatedly I have heard, that on linux it is not possible to
create a 
shared library that is statically bound to a runtime lib.
Boost.Build simply bails out before even trying, because of
this believe.

While I do understand that this is questionable practice in
general, or 
as the boost auto_link headers tell: "Mixing a dll
boost library with a 
static runtime is a really bad idea...", I was
wondering if the "not 
possible" also is true.

Though in practice I can imagine situations where it might
be useful to 
be able to do this: Shipping a shrink wrapped lib; need to
be able to 
link to two different runtime libs; creating a lib that will
link to a 
foreign language e.g. C ; ...
(your idea here) ...

I know these examples are not tremendously convincing. But
knowing where 
the borders really are can be a helpful thing.

So I grabbed the man pages and created the attached
example.

I am sure I overlooked something fundamental  but the
example 
seemingly works.

I would be glad to hear opinions of experts in this field.

Roland aka speedsnail

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build