Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!rex!uflorida!kluge!serss0!acmfiu
From: acmfiu@serss0.fiu.edu (ACMFIU)
Newsgroups: comp.sys.apple2
Subject: Re: Zaplink Question
Message-ID: <2762@kluge.fiu.edu>
Date: 7 Mar 91 01:42:21 GMT
References: <9103032217.AA18834@apple.com>
Sender: news@kluge.fiu.edu
Organization: Florida International University, Miami
Lines: 27

In article <9103032217.AA18834@apple.com> STEIN@UCONNVM.BITNET (Alan Stein) writes:
>I'm trying to put together my own generic shell, sort of like hodgepodge,
>out of small components.  So far, I have about six different source files.
>When I compiled them, and then tried to link the object files, I got a
>"expanding file names made the line too long" message from the Orca Shell.
>
>Is there a limit on the number of files that can be linked?  How do I get
>around this problem without combining source files?  Can object files be
>combined prior to linking?  Can linking be done in stages?

Alan,
	Because of the limited length of command-lines in the current
	Orca shell (this will be changed in the 2.0 shell), you cannot put
	a great deal of information on the command-line. According to the
	ZapLink documentation, you can, however, put all your link files
	into a single file with auxtype 'linker' (i.e. change <file> linker).
	your file might look somethin like this:
		file1		/* i don't know if you need .a or .root */
		file2
		file3
		file4
		file5

	and then you save it and link like so:
		compile <filename> keep=executable

albert