delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/04/08/18:29:37

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Re: Gcc/ld and long command lines (> 32k)
To: cygwin AT cygwin DOT com
Date: Thu, 8 Apr 2004 18:28:39 -0400 (EDT)
MIME-Version: 1.0
Message-Id: <20040408222839.0AE5510C7CF@perpugilliam.csclub.uwaterloo.ca>
From: rridge AT csclub DOT uwaterloo DOT ca (Ross Ridge)

> Several replies mentioned the possibility of making several
> intermediate libraries. I'm well aware of that possibility.  But since
> I'm not interested in the "library functionality" of libraries, any such
> partitioning seems artificial. I always want a *full linking* where all
> object files are needed.

You can try using an implicit linker script.  Create a file, call it
something like "my-ld-script", with lines like the following:

	INPUT(obj1.o obj2.o obj3.o)
	INPUT(obj4.o, obj5.o, obj6.o)
	INPUT(obj7.o)

And then instead of linking with a command that looks something like this:

	gcc -o foo.exe obj1.o obj2.o ... obj7.o -lbar -lbaz

Use something like this:

	gcc -o foo.exe my-ld-script -lbar -lbaz

						Ross Ridge


-- 
 l/  //	  Ross Ridge -- The Great HTMU
[oo][oo]  rridge AT csclub DOT uwaterloo DOT ca
-()-/()/  http://www.csclub.uwaterloo.ca/u/rridge/ 
 db  //	  

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019