From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10302042053.AA13981@clio.rice.edu>
Subject: Re: djgpp/manifest fixed; mkdist11.bat/nobins patch
To: djgpp-workers AT delorie DOT com
Date: Tue, 4 Feb 2003 14:53:15 -0600 (CST)
In-Reply-To: <3E401A70.5106364B@phekda.freeserve.co.uk> from "Richard Dawe" at Feb 04, 2003 07:54:24 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > Want to add this line to mkdist1.bat (to automatically build nobins if
> > it doesn't exist):
> >   cp manifest/%1.mft manifest/%1.tmp
> > + if not exist distrib\nobins.exe gcc -s -O2 distrib/nobins.c -o distrib/nobins.exe
> >   distrib\nobins @distrib/p/%1/nobins < manifest\%1.tmp > manifest\%1.tm2

> What happens if gcc fails to build nobins.exe? I think it should exit cleanly.

Is that really necessary, given the procedure continues on all other
failures (such as run-time aborts, missing images, etc?)  Right now 
there is no makefile or instructions that nobins should be built at all,
it just spews error messages the first time you run it, you see them
and fix it ...

Definitely expert driven software :-)

We could add another "if not exist" after the first one and jump to
a new label - but it really needs errorlevel checks on everything
if you plan to make it robust.

(I didn't have zip in my djgpp path, and the Win2K find was before
the djgpp one - so the procedure just needs to be watched ...)