$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-06 07:16:50
On Monday 06 June 2005 15:32, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> > 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.
>
> It's standard practice in the UNIX world to reflect the actual 0th
> argument rather than hardcoding the name IIUC.
Hmm.. I've checked with "/bin/ls" and it's indeed the case.
Craig, I've committed your patch. Thanks!
- Volodya
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2