From: sl AT psycode DOT com DOT REMOVE_THIS
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE, commandline-line and linking
Date: 5 Aug 1998 19:42:42 GMT
Organization: http://www.supernews.com, The World's Usenet: Discussions Start Here
Lines: 19
Message-ID: <iCdMCj1ZQ5j2-pn2-J5rLddf6Qqd5@portX67.lanzen.net>
References: <m0z43tk-000S4fC AT inti DOT gov DOT ar> <iCdMCj1ZQ5j2-pn2-u2Hjd1eiSfbu AT portD18 DOT Generation DOT NET> <35C89BB3 DOT D96041E9 AT cartsys DOT com>
NNTP-Posting-Host: 205.205.70.86
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Wed, 5 Aug 1998 17:51:47, Nate Eldredge <nate AT cartsys DOT com> wrote:

> A better option might be to group them into libraries, which will dodge
> the long line problem.  And don't worry about all the .o files in the
> library-- libc has a few hundred .o files inside it.

	Yeah, but like you said, that's a work around 'cuz its a library. I 
am distributing freeware libraries in source-code form and therefore I
don't know how appropriate it would be for me to make libraries out of
them. Most people (including myself) don't even know how to create a 
libraries, so how I can expect them to know how to unpack a library in
order to get at the source codes? :)

	But you did answer my question, DJGPP uses a transfer buffer.. I 
thought the problem was we had to list all .o files through the 
command line (by running GCC <parameters> <.o files>) and that would 
have been a problem..

Gili