writing (Gnu)MAKE in Python

[John Schmitt]

This is a very good question, and if I'd answered it originally, I would
have generated less traffic.

I've always thought that I was handy enough at writing makefiles on whatever
platform.  Recently I've come across a very complicated makefile (that calls
sed and grep from bash), and under most Windows' it does not work very well.
I can get by with MKS, but we have been told that we cannot require our
customers to install MKS.  (Hey, can I just pull out the GNU binaries and
drop them into our SDK and distribute that?)  (On another note, does anyone
actually do this: grep for the string "CFLAGS" in a C source file, and add
that to your compile rule?  Seems too kludgy to me, but I've seen it.)  Make
bombs out with memory problems under NT and 98 sometimes, I can't quite
predict its foreslash and backslash behaviour (although I think I've got it
down now), and Make's process for finding a shell is incomprehensible.

Another reason is that I'd like to have exactly one development environment
on all platforms, even my Mac.  Sadly, until OS X, the GNU standard UNIX
stuff won't be available on the Mac.

Anyway, I think I might be able to make a strong Python case if I could say
that we would have many fewer problems on all our platforms.  I'm almost
done with this project, and then I'll enforce the cross-platform
requirements.

Not-nearly-as-clever-as-I-imagined-my-self-ly,
more-humbly-yours-ly,

John

-----Original Message-----
From: python-list-admin at python.org
[mailto:python-list-admin at python.org]On Behalf Of Courageous
Sent: Saturday, June 17, 2000 12:17 AM
To: python-list at python.org
Subject: Re: writing (Gnu)MAKE in Python



> In a smaller way, I would like to have Bash, sed, and grep as Python
> programs rather than compiled C.

Why?



C/
--
http://www.python.org/mailman/listinfo/python-list