Message-Id: <199807080047.BAA20746@sable.ox.ac.uk>
Comments: Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: Gisle Vanem <giva AT bgnett DOT no>
Date: Wed, 8 Jul 1998 01:46:50 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: linking huge project
Reply-to: george DOT foot AT merton DOT oxford DOT ac DOT uk
CC: djgpp AT delorie DOT com
Precedence: bulk

On  7 Jul 98 at 9:22, Gisle Vanem wrote:

> The rule should of course be:
> 
> libfile.a:
>        ar rvs libfile.a @&&|
>          $(OBJS)
> |
> 
> Borland's Make would then create a temporary response file with all
> $(OBJS) listed. Like `ar rvs libfile.a @make0001.@@@'.
> 
> Now, does GNU make have anything similar?

Something like:

libfile.a:
        @echo $(OBJS) > $(TEMPFILE)
        ar rvs $@ @$(TEMPFILE)
        @rm -f $(TEMPFILE)

but with the filename assured to be writable, and assured not to
clash with another file?  It doesn't seem very useful; you could use
it to call old djgpp programs, or non-djgpp programs.  It would be
pretty trivial to make a djgpp v2.01 program capable of calling other
programs in this way of course.

In general I don't think it's a good idea to call non-djgpp programs 
from djgpp programs though; sometimes it doesn't work properly (e.g. 
if the other program tries to use 16-bit DPMI).

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk