Opened 13 years ago
Last modified 12 years ago
#3550 assigned Bugs
specify toolset to bootstrap.bat
| Reported by: | Owned by: | Vladimir Prus | |
|---|---|---|---|
| Milestone: | Boost 1.46.0 | Component: | Building Boost |
| Version: | Boost 1.40.0 | Severity: | Cosmetic |
| Keywords: | bootstrap.bat bjam.exe bin.ntx86_64 | Cc: |
Description
Hi,
calling "bootstrap.bat" results in successful compilation of boost_1_40_0\tools\jam\src\bin.ntx86_64\bjam.exe but this is not where the bootstrap.bat expects it to be, as it only supports x86 as it seems.
BTW: tools\jam\src\build.bat somehow finds my VS2010beta and uses that for compilation (although I'd like it to use my production VS9) and it seems I have no control of telling "bootstrap.bat" to use a custom toolset (this is supported by build.bat)
cheers Chris
Attachments (4)
Change History (12)
by , 13 years ago
| Attachment: | bootstrap.bat added |
|---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Hi,
works like a charm. However, I think you missed to insert "if exist ".\tools\jam\src\bin.ntx86_64\bjam.exe" del tools\jam\src\bin.ntx86_64\bjam.exe" at line 10?!
The VS2010 toolset is not a showstopper, as I can still set the toolset "msvc-9.0" when calling bjam.
Just as a suggestion: you could accept the toolset as argument to bootstrap.bat, just forward it to build.bat, which would have the additional advantage of producing a correct "project-config.jam". I guess the latter is read by bjam?!
comment:3 by , 13 years ago
Hi.
Indeed, I should have added that line. I've now done so, and committed the change to the trunk and release branches.
As for passing toolset, could you try running the attached -- both without arguments and with 'vc9'? Note that unfortunately, this will not affect project-config.jam as there are some issue with making tools/jam/src/build.bat report the toolset it has used.
by , 13 years ago
| Attachment: | bootstrap.2.bat added |
|---|
Version that forward toolset over to bjam's build.bat
comment:4 by , 13 years ago
| Milestone: | Boost 1.41.0 → Boost 1.42.0 |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
The toolset forwarding is probably for 1.42 now.
comment:5 by , 12 years ago
| Version: | Boost 1.40.0 → Boost 1.45.0 |
|---|
Update milestone. Please mark this one appropriately or fix it for 1.45. Thanks.
comment:6 by , 12 years ago
| Milestone: | Boost 1.42.0 → Boost-1.45.0 |
|---|---|
| Version: | Boost 1.45.0 → Boost 1.40.0 |
Whoops, change milestone, not version.
comment:7 by , 12 years ago
| Milestone: | Boost-1.45.0 → Boost-1.46.0 |
|---|---|
| Severity: | Showstopper → Cosmetic |
| Summary: | bootstrap.bat not running on x64 Windows → specify toolset to bootstrap.bat |
The fix for 64-bit windows has been checked in long ago. The reminder of this bug is about specifying the toolset for Boost.Build bootstrapping (that is, building bjam). That issue is definitely not a showstopper
comment:8 by , 12 years ago
I've added functionality to the two batch files to pass BOOST_JAM_TOOLSET (the toolset ultimately used) from build.bat back to bootstrap.bat via a BOOST_JAM_TOOLSET.txt.
Chris, thank you for the report. Can you try the attached version of bootstrap.bat -- it should find the 64-bit bjam after it is build. If it works, I'll merge it for 1.41.
As for vc9 vs. vc10 -- is it affecting only compilation of bjam itself, or causing other problems? If it's affecting bjam itself, this is probably not a 1.41 showstopper.
Thanks, Volodya