Re: Do not hardcode binary name in usage message?

From: David Abrahams (dave_at_[hidden])
Date: 2005-06-06 06:32:52

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.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com