Boost-Build :

Date view	Thread view	Subject view	Author view

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-06 05:09:39

Next message: Vladimir Prus: "Re: [jamboost] Re: [v2] Overuse of response files?"
Previous message: Vladimir Prus: "Re: [jamboost] [v2] Incomprehensible error when boost-build.jam missing."
In reply to: Craig Rodrigues: "Do not hardcode binary name in usage message?"
Next in thread: David Abrahams: "Re: Do not hardcode binary name in usage message?"
Reply: David Abrahams: "Re: Do not hardcode binary name in usage message?"

Hi Craig,

> Since the Boost Jam build produces a binary called "bjam"
> and not "jam", should the "usage" message reflect this?

That might produce output like:

usage: bin.linuxx86/bjam [ options ] targets...

is the path desired? Maybe, we should just hardcode "bjam", as we don't
care much about classic Jam compatibility, and "jam" binary is no longer built
by default.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2

Next message: Vladimir Prus: "Re: [jamboost] Re: [v2] Overuse of response files?"
Previous message: Vladimir Prus: "Re: [jamboost] [v2] Incomprehensible error when boost-build.jam missing."
In reply to: Craig Rodrigues: "Do not hardcode binary name in usage message?"
Next in thread: David Abrahams: "Re: Do not hardcode binary name in usage message?"
Reply: David Abrahams: "Re: Do not hardcode binary name in usage message?"

Date view	Thread view	Subject view	Author view

Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk