Is it me, or does the "announce" forum seem a bit stale? From what I can tell,
the most recent message appearing there is from 4-23, and i'm fairly sure that
other stuff has gone out since then that doesn't show up (like the weekly news
#59 sent on 4-29). Could this be a problem with the forum,
> > So please let me know which of the following are desirable, need changes
> > or are simply evil:
>
> While you're there, I'd suggest trying to bring it back into sync with
> nightly. It always drifts over time (it's a little obscure), and one
> bit of difference in there now is the con
Gavin Maltby writes:
> So please let me know which of the following are desirable, need changes
> or are simply evil:
While you're there, I'd suggest trying to bring it back into sync with
nightly. It always drifts over time (it's a little obscure), and one
bit of difference in there now is the c
Hi Darren,
On 05/09/07 14:30, Darren J Moffat wrote:
Gavin Maltby wrote:
- if NIGHTLY_OPTIONS from the env file selects 'd' for dmake then:
. /opt/teamware/bin is added to the PATH
. if DMAKE_MAX_JOBS is not already set then groks this out of
~/.make.machines (otherwise every dmak
Gavin Maltby wrote:
- if NIGHTLY_OPTIONS from the env file selects 'd' for dmake then:
. /opt/teamware/bin is added to the PATH
. if DMAKE_MAX_JOBS is not already set then groks this out of
~/.make.machines (otherwise every dmake parses that file);
. if no setting in .make.machi
Hi
I have a private modified bldenv variant which adds a few features
described below. To share with others, and to avoid my having
to merge changes to my private copy, I'll polish it up for putback
of any features others think are desirable.
So please let me know which of the following are des
