Boost C++ Libraries: Ticket #3280: stage directory does not appear where guide claims with build-dir https://svn.boost.org/trac10/ticket/3280 <p> In section 5.3.4 the guide for Windows claims that the stage directory will appear inside the build-dir. </p> <p> It actually appears in the boost tree root (the cwd). </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/3280 Trac 1.4.3 Dave Abrahams Wed, 22 Jul 2009 00:33:01 GMT owner changed https://svn.boost.org/trac10/ticket/3280#comment:1 https://svn.boost.org/trac10/ticket/3280#comment:1 <ul> <li><strong>owner</strong> changed from <span class="trac-author">Dave Abrahams</span> to <span class="trac-author">Vladimir Prus</span> </li> </ul> <p> Should this be considered a Boost.Build bug or a GSG doc bug? I.e., is this behavior intentional? </p> Ticket Vladimir Prus Wed, 22 Jul 2009 05:16:53 GMT owner changed https://svn.boost.org/trac10/ticket/3280#comment:2 https://svn.boost.org/trac10/ticket/3280#comment:2 <ul> <li><strong>owner</strong> changed from <span class="trac-author">Vladimir Prus</span> to <span class="trac-author">Dave Abrahams</span> </li> </ul> <p> 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. </p> Ticket Dave Abrahams Wed, 22 Jul 2009 12:42:40 GMT <link>https://svn.boost.org/trac10/ticket/3280#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3280#comment:3</guid> <description> <p> OK. Is there a separate setting for --stage-dir ? It's almost as though what we want is </p> <blockquote> <p> <code>bjam --stage=</code><em>stage-directory</em> </p> </blockquote> <p> with no target needed. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Steven Watanabe</dc:creator> <pubDate>Thu, 10 Jun 2010 00:16:15 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/3280#comment:4 https://svn.boost.org/trac10/ticket/3280#comment:4 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> (In <a class="changeset" href="https://svn.boost.org/trac10/changeset/62702" title="Give the correct location for stagedir. Fixes #3280.">[62702]</a>) Give the correct location for stagedir. Fixes <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/3280" title="#3280: Bugs: stage directory does not appear where guide claims with build-dir (closed: fixed)">#3280</a>. </p> Ticket Steven Watanabe Thu, 10 Jun 2010 00:17:46 GMT <link>https://svn.boost.org/trac10/ticket/3280#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3280#comment:5</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/3280#comment:3" title="Comment 3">dave</a>: </p> <blockquote class="citation"> <p> OK. Is there a separate setting for --stage-dir ? It's almost as though what we want is </p> <blockquote> <p> <code>bjam --stage=</code><em>stage-directory</em> </p> </blockquote> <p> with no target needed. </p> </blockquote> <p> Currently stage will be build by default, so </p> <pre class="wiki">bjam --stagedir=&lt;stage directory&gt; </pre><p> works. </p> </description> <category>Ticket</category> </item> </channel> </rss>