Date:	Sat, 03 Mar 2001 10:23:42 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT ZAHAV DOT NET DOT IL
To:	"Edward F. Sowell" <sowelled AT home DOT com>
Message-Id:	<2427-Sat03Mar2001102342+0200-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC:	djgpp AT delorie DOT com
In-reply-to:	<3AA03539.F5CF05AE@home.com> (sowelled@home.com)
Subject:	Re: Where does command line length limitation come from?
References:	<rvOBjBA6F8n6MAv8 AT teccon DOT co DOT uk> <3AA03539 DOT F5CF05AE AT home DOT com>
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

> From: "Edward F. Sowell" <sowelled AT home DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 02 Mar 2001 23:56:41 GMT
> 
> Also, even though the GNU make program accepts long command within
> makefiles, this does not mean that make itself can be invoked with a
> long command line. In particular, if GNU make is spawned from
> a typical PC C++ compiled program, the command line gets chopped
> to 126 characters, whereas the PC make program (nmake, smake, Borland make)
> do not. The only work-around is to compile the program
> from which the spawn call to GNU make is made with g++.

That's not the only work-around.  You can also use the response file
method for invoking a DJGPP program from a non-DJGPP one.

The current development sources of the DJGPP library include code
which allows to pass command lines up to 1KB from non-DJGPP to DJGPP
programs and vice versa, using the CMDLINE environment variable.  The
next DJGPP release will support this.

Note that passing long command lines from COMMAND.COM's prompt
requires some non-defualt setup of COMMAND.COM as well.

- Raw text -