🚀 go-pugleaf

fox@rei.com (Fuzzy Fox) writes:

> levin@world.std.com (Levin F Magruder) writes:
> 
> >With the make & tlink that come with BCC 2.0, how do you set
> >things up so that you only need to maintain a single list of
> >object files?
> 
> >I defined a macro in make like:
> >OBJECTS=a.obj b.obj ....
> 
> >prog.exe: $(OBJECTS)
> >    tlink \bc\t0s.obj $(OBJECTS), progname, , ...
> 
> >worked until the command line overflowed.
> 
> You will always run into this problem anytime you try to put $(OBJECTS)
> onto a command line.

with BCC 2.0, that should be make 3.0, yes?  If so, the solution is to
have make build a response file on the fly...

prog.exe: $(OBJECTS)
    tlink @&&|
\bc\t0s.obj $(OBJECTS)
$*
$*
\bc\ts.lib other\libs\here
|

I do this all the time, and it saves having to keep a linkfile in sync
with the project.
--
Roy M. Silvernail --    [my machine ] "Sometimes, you're the windshield....
roy%cybrspc@cs.umn.edu  [my opinions]            sometimes, you're the bug!"
cybrspc!roy@cs.umn.edu  [my $0.0275 ]                      --Mark Knopfler