Makefiles (was: MOSE)

Topic: Makefiles (was: MOSE) (Read 12999 times) previous topic - next topic

Makefiles (was: MOSE)

February 25, 2010, 11:19:29 am

Why would you write a whole new tool, instead of using GNU 'make' -- www.gnu.org/software/make/ -- which takes care of defining variables, examining dependency trees, and running all programs... and is standard on any modern system?

(not being argumentative, just curious)

Makefiles (was: MOSE)

Reply #1 – February 25, 2010, 02:59:36 pm

Here's your answer:

Quote

C:\Documents and Settings\Vladimir>make
MAKE Version 5.2 Copyright (c) 1987, 2000 Borland

Makefiles (was: MOSE)

Reply #2 – February 25, 2010, 03:36:43 pm

Don't use Borland make. Use GNU make. GNU make is GPL'd, has been for a decade at least.

http://gnuwin32.sourceforge.net/packages/make.htm

Makefiles (was: MOSE)

Reply #3 – February 25, 2010, 05:44:34 pm

Then it's a question of installing make versus installing Python. As I'm on windows, the choice is size vs. fiddling with PATH.

If you want to start tearing your hair out, pak128 also uses its own tool.

Re: Makefiles (was: MOSE)

Reply #4 – February 28, 2010, 01:52:30 pm

So I see, pak128 has a custom tool. I've read through it and it seems to be rewriting GNU make...

pak64 uses a regular Makefile, which works perfectly... why re-invent the wheel?

I will be using pak64's build model in pak128.USA

Re: Makefiles (was: MOSE)

Reply #5 – February 28, 2010, 05:17:50 pm

For one, about every genial developer had the great idea that "make" is a name free to take, so I have a lot of makes around, each of them needed by something (my previous post is just a preview

). Secondly, even with GNU make the pak64 makefile does not work perfectly around here. Looks like MAKEOBJ ?= ./makeobj makes it *nix-specific, not to mention rm and cp and all that. So... sorry, but this just doesn't cut it for me. Also there is no good recursion, which I prefer to all the folders listed in one place. The few hours I spent writing that one script in Python can be hardly compared with the 20+ years of make, yet my script runs on two major os cores just fine... what can I fix by switching?

Quote

D:\Hry\Simutrans\DEV\64svn>mingw32-make
"===> COPY"
Nesprávná syntaxe příkazu
mingw32-make: *** [copy] Error 1

D:\Hry\Simutrans\DEV\64svn>mingw32-make zip
mingw32-make: *** No rule to make target `simutrans/pak', needed by `simupak64.zip'. Stop.

D:\Hry\Simutrans\DEV\64svn>mingw32-make tar
mingw32-make: *** No rule to make target `simutrans/pak', needed by `simupak64.tbz2'. Stop.

D:\Hry\Simutrans\DEV\64svn>mingw32-make clean
"===> CLEAN"