home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!utcsri!geac!r-node!zooid!ross
- From: Ross Ridge <ross@zooid.guild.org>
- Subject: Re: BCC 2.0: What is the right way to use make & tlink?
- Organization: ZOOiD BBS
- Date: Sat, 5 Sep 1992 06:51:44 GMT
- Message-ID: <1992Sep5.065144.13637@zooid.guild.org>
- References: <Bu15L0.J1z@world.std.com>
- Lines: 38
-
- levin@world.std.com (Levin F Magruder) writes:
- >prog.exe: $(OBJECTS)
- > tlink \bc\t0s.obj $(OBJECTS), progname, , ...
- >
- >worked until the command line overflowed. So, I had to make a
- >response file for tlink. And now I have to remember to update
- >both lists as I add modules.
- >
- >There must be some feature I am missing?
- >
- >If I'm *not* missing someone, someone here could probably write
- >a program in about 20 minutes that reads a list of file names
- >and spits out two files, an inclusion file for make and a response
- >file for tlink. Or tell me some other intelligent way to do
- >this?
-
- I have the Makefile create the response file automatically
- when building libraries, it should work for linking just as well:
-
- mytinfo.lib: libcmd $(OBJS1) $(OBJS2) $(OBJS3) $(OBJS4)
- del mytinfo.lib
- $(AR) mytinfo.lib @libcmd
-
- libcmd: makefile
- echo $(ARFLAGS) & > libcmd
- for %i in ($(OBJS1)) do echo + %i & >> libcmd
- for %i in ($(OBJS2)) do echo + %i & >> libcmd
- for %i in ($(OBJS3)) do echo + %i & >> libcmd
- for %i in ($(OBJS4)) do echo + %i & >> libcmd
- echo , >> libcmd
-
- Ross Ridge
-
- --
- Ross Ridge - The Great HTMU l/ //
- [OO][oo]
- ross@zooid.guild.org /()\/()/
- uunet.ca!zooid!ross db //
-