The Makefile in packaging seems to think it's a shell script. Quoting: > # Build and install step by step. > # > # e.g. to build gcc, it is required to have a working msp430 binutils this > # is ensured by first building and installing them, then building and > # installing gcc and so on. > # > # On Windows, stripfiles must be called before the python tools are installed > # or they will be broken. > build: binutils-build binutils-install \ > gcc-build gcc-install \ > msp430-libc-build msp430-libc-install \ > gdb-build gdb-install \ > libmspgcc-build libmspgcc-install \ > stripfiles \ > pytools-build pytools-install \ > libraries-build libraries-install
make has a facility called "dependencies" to make sure that builds are executed in the proper order. For example, the gcc-build target could specify binutils-install as a dependency so that Make would build it first. The shell-script approach is a failure for several reasons. One reason is that make -j will not be able to parallelize properly without understanding the actual dependency graph. Another reason, one that's bothering me right now, is that when a build bombs out, I cannot go edit the file that's causing the problem, and restart the build. It will start building over from the beginning, which takes a long time. Regards, Mark markra...@gmail -- Mark Rages, Engineer Midwest Telecine LLC [email protected]
