Re: [boost] [1.47.0] Release candidate files available

Subject: Re: [boost] [1.47.0] Release candidate files available
From: Beman Dawes (bdawes_at_[hidden])
Date: 2011-07-11 13:21:45

On Mon, Jul 11, 2011 at 8:38 AM, KTC <ktc_at_[hidden]> wrote:
> On 10/07/2011 22:57, Beman Dawes wrote:
>>
>> Release candidate files for 1.47.0 are available at
>> http://boost.cowic.de/rc/
>>
>> As always, the release managers would appreciate it if you download
>> the candidate of your choice and give building it a try. Please report
>> both success and failure, and anything else that is noteworthy.
>
> File: boost_1_47_0.7z
>
> Setup:
> <http://www.boost.org/development/tests/release/KTC-Win7x64_VC10x64.html>
>
> Command:
>    b2 --stagedir=x64 --build-type=complete -j2 architecture=x86
> address-model=64 stage
>    b2 --with-python --stagedir=x86 --build-type=complete -j2 stage
>    b2 --without-python --stagedir=x86 --build-type=complete -j2 stage
>
> All built without errors.

Good! Thanks for the multiple tests!

> However, I want to know why bootstrap.bat creates
> both a bjam.exe & a b2.exe, where then both are copied to <BOOST_ROOT>.

IIUC, "bjam" is being "rebranded" as "b2" to reduce confusion between
jam and boost build. Presumably both names are being supported so that
user scripts using "bjam" still work.

> Also, in 1.46.1 --build-type=complete created 476 files, whereas here (with
> b2.exe) it created 280 / 290 for x64 & x86 targets respectively.

Hum... I'm clueless on that one.

--Beman