Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#3280 closed Bugs (fixed)

stage directory does not appear where guide claims with build-dir

Reported by: Lars Viklund <zao@…> Owned by: Dave Abrahams
Milestone: Boost 1.40.0 Component: Getting Started Guide
Version: Boost 1.39.0 Severity: Problem
Keywords: getting started stage Cc:

Description

In section 5.3.4 the guide for Windows claims that the stage directory will appear inside the build-dir.

It actually appears in the boost tree root (the cwd).

Change History (5)

comment:1 by Dave Abrahams, 13 years ago

Owner: changed from Dave Abrahams to Vladimir Prus

Should this be considered a Boost.Build bug or a GSG doc bug? I.e., is this behavior intentional?

comment:2 by Vladimir Prus, 13 years ago

Owner: changed from Vladimir Prus to Dave Abrahams

To the best of my knowledge, this is the behaviour V1 had. It seems somewhat reasonable to me, if --build-dir is though as 'place where intermediate products go'. So, I think GSG is to be updated.

comment:3 by Dave Abrahams, 13 years ago

OK. Is there a separate setting for --stage-dir ? It's almost as though what we want is

bjam --stage=stage-directory

with no target needed.

comment:4 by Steven Watanabe, 12 years ago

Resolution: → fixed
Status: new → closed

(In [62702]) Give the correct location for stagedir. Fixes #3280.

in reply to:  3 comment:5 by Steven Watanabe, 12 years ago

Replying to dave:

OK. Is there a separate setting for --stage-dir ? It's almost as though what we want is

bjam --stage=stage-directory

with no target needed.

Currently stage will be build by default, so 

bjam --stagedir=<stage directory>

works.

Note: See TracTickets for help on using tickets.