9 messages in com.perforce.jammingcommand line limit
FromSent OnAttachments
Sush...@crow.bmc.com Sushama_Kazi@crow.bmc.com12 Nov 1998 13:54.rtf, .rtf
Laur...@perforce.com12 Nov 1998 15:07 
Rand...@inven.com13 Nov 1998 08:42 
chri...@natinst.com chris.bartz@natinst.com13 Nov 1998 09:36 
Step...@alum.mit.edu13 Nov 1998 10:01 
Laur...@perforce.com13 Nov 1998 10:40 
Jym ...@igc.org13 Nov 1998 11:03 
Sush...@crow.bmc.com Sushama_Kazi@crow.bmc.com13 Nov 1998 15:41.rtf, .rtf
"Cowham, Robert Associate CowhamR@logica.com16 Nov 1998 04:15 
Subject:command line limit
From: ()
Date:11/16/1998 04:15:28 AM
List:com.perforce.jamming

I had to implement something very similar for our VMS builds (echoing to a .opt file). Bit of a pain, and not as neat as the recent suggestions, but it worked.

Robert

-----Original Message----- From: jy@igc.org [mailto:jy@igc.org] Sent: 13 November 1998 19:04 To: jamm@perforce.com Subject: Re: command line limit

The actual limit in NT 4.0 is still far to short for linking a large project.

=o= Yeah, the rationale for this goes all the way back to the days of VMS (which NT is but a cheap knock-off of): if you need to link more files than will fit on the command line, you need to list them in a file. Under VMS this was called an "options" file (with an ".opt" suffix), and there were some options in particular that you could *only* specify there.