Further Adventures w/MS Make
Physically Pffft
jlh at loral.UUCP
Thu Aug 18 07:38:23 AEST 1988
In article <1148 at gethen.UUCP> doug at gethen.UUCP (Doug Asherman) writes:
=I am (again) having a slight problem with the Microsoft make utility.
=I'll go through this step by step...bear with me, OK?
=
=I have the following inference rules set up in TOOLS.INI in the UTIL
=directory:
=
=a.obj : a.c
=
=b.obj : b.c
=
=demo.exe : a.obj b.obj
=#end of makefile
=
= The problem here is: a.obj and b.obj are both built successfully.
=However, demo.exe is not created. If I change the name of either a or
=b to demo, though, everything goes without a hitch.
If memory serves me correctly you hafta put the demo.exe: line ABOVE the
a.obj and b.obj. Microsoft make is pretty stupid, almost as stupid as
the user interfaces to the compiler and linker. Too bad you can't use
a 'good' make, like Aztec's, but then I run into lots of problems with
the linker interface. Stuff like the Aztec make lets me make a line
longer than 128 characters, but the linker stops parsing the input line
at 128 with no warning or message whatsoever. Because the 128 limit
fell on a space between my source file specifications and my library
specification it took me 2 days to figure out why the bloody linker
refused to include my libraries. Microsoft make gives the error message
'line too long'.
Jim
"Broken spanish spoken perfectly"
--
Jim Harkins
Loral Instrumentation, San Diego
{ucbvax, ittvax!dcdwest, akgua, decvax, ihnp4}!ucsd!sdcc6!loral!jlh
More information about the Comp.lang.c
mailing list