kicad-developers team mailing list archive

["Chris Albertson" <albertson.chris@...>]

On 10/31/07, Richard A Burton <richardaburton@...> wrote:

> I'd like to get rid of the recursive make calls too, it's not good
> practise. For one thing when part of the build fails the overall make
> doesn't fail, which is not ideal for automated package building.

Keep the recursive makefile. What should be lost is the "-k" option
that causes make to continue after a error. Having a Makefile in each
directory allows one to type "make" when you are in a lower level
directory editing files. For example I have some supporting libraries
and when in there I can run "make check" for an automated unit test.
Very good after making a change. But you are right make should fail
on an error.

I'll still argue for using GNU autoconf. The current method does not
scale. What happens if you want to build on a few more platforms?
At work My stuff needs to work on Linux (two different distributions)
and on Solaris 8 and Solaris 10 with GNU gcc (3x and 4x)and Sun's
"Studio 11" compiler. No way would I want to maintain multiple makefile.
I just list the files in Makefile.am and that's it. I find now that my code
will compile on platforms I've never seen before

I just installed The new Mac OS X "Leopard". I'm going to see if
I can build Kicad on it now






-- 
=====
Chris Albertson
Redondo Beach, California