🚀 go-pugleaf

Dear friends,

   Thank you for the many kind letters explaining that LMK will
indeed recompile a touched .c file.

   I'd like to change my description of my problems with LMK to
the following:

    "While I am very fond of the Lattice 5.0 development environment
     and am certain that LMK is a useful tool for many programmers,
     I find that it is insufficiently compatible with the make
     programs to which I am accustomed, and am therefore looking
     for alternatives."

Here's an example makefile that it can't handle.  The several big
problems I've had are all relating to the include dependency line.
If I remove it, I think I can use LMK in the interim.  (Note that
I'm working on some projects considerably more complicated than
hello.c ;^)

I've reported all problems and their support is extremely responsive,
but I don't anticipate a fix to this problem soon.

	jimm

# lattice development test makefile

LC1FLAGS=-iINCLUDE: -d

.c.o:
	lc1 $(LC1FLAGS) -oquad:$*.q $* 
	go quad:$*.q
	lc2 -o$*.o quad:$*.q 

.o.lst:
	omd >$*.lst $*.o $*.c

LIBS=lib:lc.lib

OBJS=hello.o foo.o

hello: $(OBJS)
	blink FROM lib:c.o $(OBJS) LIB $(LIBS) TO $@

hello.lst: hello.o

# this is what confuses LMK, keeping it from updating hello.o when
# hello.c is changed.  Also, if you touch foo.c, it recompiles hello.c.
# I had this line once when foo.o was created from foo.asm.
# In that case, I think it tried to compile hello.asm when foo.asm
# was touched.
#
# I reported this behavior and the response was that contrary
# to my assertion, this was not the standard way of making
# dependencies on include files.

foo.o hello.o: hello.h

-- 
Jim Mackraz, I and I Computing	   	"Like you said when we crawled down
{cbmvax,well,oliveb}!amiga!jimm          from the trees: We're in transition."
							- Gang of Four
Opinions are my own.  Comments are not to be taken as Commodore official policy.