< / rant on >
I have one other thing to say about makefiles and that is that a lot of
the big makefile systems I have seen are wrong and use recursion to
solve problems that only cause more problems than they solve. Have a
look at this paper http://aegis.sourceforge.net/auug97.pdf I found it
after I wrote the makefile I posted to this list but this has changed
the way I write big makefiles and I would say speed up compile times in
some cases by as much as 100-times.
Makefile programming is becoming a lost art at least in the circles I
have travelled in I have yet to meet anybody who knows more about
makefile than myself and I still look up the manual when I want to do
< / rant off >
Dave I could not agree with you more if any one is interested I could
port the makefile I posted here so that it will work on windows.
Dave McGuire wrote:
> On Nov 16, 2004, at 3:02 PM, Rod Boyce wrote:
>> make file programming is a lost art I. Most developers I have seen
>> are quite lazy and would prefer to use a GUI.
> In the PC world, perhaps. However, in the world of large software
> development projects (non-embedded operating systems for example),
> GUIs are most definitely not the mainstay of development.
> Personally, however, I use makefiles because I am lazy. :) I just
> don't have the patience to deal with the maze of inconsistent,
> often-unstable GUIfied "programming" tools.
> Now, that said, I like GUIs as much as the next guy...but
> programming is a textual task, and probably always will be. Just
> because one can GUIfy a task doesn't necessarily mean one should.
> Just my opinion.
> Dave McGuire "I wonder what 'Error Code 1' means. That's
> Cape Coral, FL what it said when it started smoking."
> -Jonathan Patschke
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. http://www.intersystems.com/match8
> Sdcc-user mailing list