On 2006-03-19, Francisco Silva <fran...@gmail.com> wrote: >> I always create a shell-script that builds/installs the entire >> toolchain (binutils, gcc, gdb and libraries) from source >> tarballs and directories of patch files. Then I archive the >> build script, source tarballs, and patches. > > Take a look in the packaging subdirectory in the mspgcc CVS > repository. There is a very clever makefile that fetches all the > sources and builds the complete toolchain in a single command.
I saw that, but I don't like scripts auto-fetching things. I want to know without a doubt that the build script is using the exact same tarballs+patches each time I run it. Besides, I already had a toolchain build script that I'd been using for some other targets, and modifying it to build for the MSP430 target was pretty trivial. -- Grant Edwards gra...@visi.com
