Date: Sun, 4 Feb 2001 17:25:01 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: April <awhite AT user DOT rose DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: shelling out to run 'ar'
In-Reply-To: <3A7D6E7D.A26C95B@user.rose.com>
Message-ID: <Pine.SUN.3.91.1010204172239.26840C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 4 Feb 2001, April wrote:

> I am playing with an editor program, and I started making it create libs
> from .o files.  During developement I show the command line I am
> shelling out to "....\ar.exe rcs libdelta.a  Appver.o .... version.o"
> which works fine if I copy and paste it to the Win95 command line, but
> when shelling out, AR reports an error 'unknown option e'
> 
> I am using the Win32api CreateProcess() to shell out - which is working
> fantastic for GCC compiling and linking, as well as the resource
> compiler - so it seems it is particular to AR.

I suspect that you are overflowing the 126-character limit of the DOS 
command line.  DJGPP programs currently don't support any method of 
passing long command lines that would work with CreateProcess.

> Does AR recognize a @batch file?

All DJGPP programs support @response-file.  See section 16.3 of the DJGPP 
FAQ.