Questions about build tools

[the-real-neil]

Questions about build tools

[michaelcmartin]

I've been digging around this a little bit so far, and this is a simple enough project that I think simple Makefiles are the way to go - were it not for the _68000.c files. this could be built with yacc macross_6502.y && gcc -m32 -o macross *.c, and then slinky with cp y.tab.h slinky && cd slinky && gcc -o slinky *.c.

The dependency of both products on the same y.tab.h is the only sticking point, really, which makes me think it could be well handled with a single simple Makefile, perhaps with a pre-run makedepend.

Be aware that I've made pretty heavy changes to the makefile and the system requirements on my fork at present; modern gcc seems to really dislike pre-ANSI C, and my fork compiles with gcc -m32 -ansi, at least.

[michaelcmartin]

Er, to clarify the earlier stuff - there already are two Makefiles in the system, but they're a bit old and dodgy. The michaelcmartin:ansi-c branch only made minor tweaks to the core logic in it and gcc or clang + yacc or bison is all you need for it to build and go. There's a couple of obvious simplifications I'd like to make to them (exploiting patternmatching in Makefiles, basically) and after that it's probably clearer whether that's all that's necessary or if there are further improvements to make.

[the-real-neil]

Thanks for the prompt reply. Good point---autotools are often overkill.

Incidentally, after glancing at the Makefile on master, it looks like both POSIX and GNU make are supported.