From: elf AT netcom DOT com (Marc Singer) Message-Id: <199610241809.LAA04295@netcom17.netcom.com> Subject: Re: Source archive for make-3.75 and long names To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii) Date: Thu, 24 Oct 1996 11:07:20 -0700 (PDT) In-Reply-To: from "Eli Zaretskii" at Oct 24, 96 02:06:45 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1055 Sender: elf AT netcom DOT com > > > It shouldn't be too hard to write a small DJGPP program that will put the > > > long command line into CMDLINE variable and invoke the program you need. > > > > Does this technique work with Win32 native programs? My client is > > using MSC10, aka Visual (ha) C++ 4.0. > > I have no idea, but I cannot imagine why not. > > Even if that doesn't work, you can change `system' and/or `spawn' in the > DJGPP library so that they will support whatever method native Win32 > programs use. Since DJGPP is free software, you can do whatever you like. Yes, of course. That is why we are all here. Yet, I'm confused. I believe that the only way to pass long command lines to Win32 programs is to call the Win32 entry point. I was not aware that we had that ability from DPMI. Please correct me, but I thought we launched programs via the DOS-style interrupt 21. Cygnus has implemented a native Win32 bin-utils package, but it works because Windows loads their program as a native binary. So, who uses the CMDLINE variable for command lines?