Makefiles [was: building Mac 2.3b VM]

Blanchard, Tod tod.blanchard at
Wed Dec 9 17:48:16 UTC 1998

No, but projects are closed, non-portable, and have short life expectancies.
I run into the "wrong version" issue all the time and if I have to move the
code elsewhere I still have to write a makefile.  Project manager should
write makefiles.

Also, large projects should be developed as a system of sub projects each
with its own makefile.  I actually have two types of makefiles - module
makefiles and project makefiles (which just call module makefiles).  I'm
gonna stay pro-makefile and anti-closed file format.

> -----Original Message-----
> From:	Ken Dickey [SMTP:kend at]
> Sent:	Tuesday, December 08, 1998 4:37 PM
> To:	squeak at
> Subject:	RE: Makefiles [was: building Mac 2.3b VM]
> >And yet Makefiles are what MacOS X and WebObjects people use to manage
> >development.
> I didn't say I don't use makefiles.  But having built large projects 
> (e.g. Sun's JDK) using both makefiles and Metrowerks projects, I find the 
> latter much easier to use.  They both have problems, but assuming 
> makefiles are easy and projects are hard is a little much.
> Cheers,
> -KenD

More information about the Squeak-dev mailing list