Re: every static library built twice ?

From: David Abrahams (dave_at_[hidden])
Date: 2003-12-20 17:10:30

"John Maddock" <john_at_[hidden]> writes:

>> > using the vc7.1 toolset I get files like:
>> > boost_date_time-vc71-mt-s-1_31.dll
>> > boost_date_time-vc71-s-1_31.dll
>> > boost_thread-vc71-mt-s-1_31.dll
>> > I'm having trouble wrapping my brain around the concept of a static dll
> or
>> > what it would mean
>>
>> Dll's shouldn't be built with a static runtime - it generally leads
>> to all kinds of memory errors - there should be a
>> <runtime-link>dynamic requirement on all the dll targets in the
>> Jamfiles, if there aren't it's a bug IMO.

I don't think it would be a bug for Boost.Python. Any DLL that
doesn't pass resources outside its boundaries can be built with a
static runtime IIUC.

> This issue should be fixed in cvs now (I've also re-enabled
> install-stage for date_time lib on NT, as this does actually work
> now).

This seems like a slightly drastic step to take without some
discussion first.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com