Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#3213 closed Feature Requests (worksforme)

Add -C (change directory) option to bjam

Reported by: Jeremiah Willcock Owned by: René Rivera
Milestone: Boost 1.40.0 Component: bjam
Version: Boost 1.39.0 Severity: Not Applicable
Keywords: Cc:

Description

GNU Make has a very useful command line flag -C (or --directory) that changes the directory to its argument before starting make. This is different than changing it in your shell because Make's change is local to its process (and its subprocesses) and does not change the outside user environment. One example of where this is useful is if I am working in boost/graph, and would like to re-run the Boost.Graph test suite. With -C, all I would need to do is:

bjam -C ../../libs/graph/test

and the tests would be run as though I changed into that directory, ran bjam, and then changed back. I believe that this feature would be very convenient. More documentation is available at http://www.gnu.org/software/make/manual/make.html#Options-Summary.

Change History (8)

comment:1 by Steven Watanabe, 13 years ago

Doesn't

bjam ../../libs/graph/test

work?

comment:2 by Jeremiah Willcock, 13 years ago

Yes -- I didn't notice that. It isn't in bjam --help, but it is likely to be in the documentation somewhere.

comment:3 by Steven Watanabe, 13 years ago

This is just part of the syntax for specifying which targets to build. In addition to what is specified at http://www.boost.org/boost-build2/doc/html/bbv2/reference/definitions.html#bbv2.reference.ids, a path to a directory is interpreted to mean the project in that directory.

comment:4 by Vladimir Prus, 13 years ago

Is there anything still to do here? Can this issue be closed?

comment:5 by Jeremiah Willcock, 13 years ago

It can as far as I'm concerned -- the functionality exists in bjam, and there's no reason to add another syntax for it.

comment:6 by Daniel James, 13 years ago

It would be useful for building documentation, as the documentation is built under the current directory. But perhaps the proper solution to that would be to fix the boostbook tool so that there's more control over where the documentation is built.

comment:7 by Vladimir Prus, 13 years ago

Resolution: worksforme
Status: newclosed

Daniel, I suspect that it is indeed better to address doc location is some other, better way. Can you file an issue telling what is bad about the current arrangement?

comment:8 by Daniel James, 13 years ago

Sure. it's #3240.

Note: See TracTickets for help on using tickets.