There's nothing special about the msp430-elf tools; you cross-build them just like any other embedded toolchain. If you can, use the latest versions of gcc, binutils, gdb, and newlib (which is typically the development head if there hasn't been a recent release). If you download the TI build of the tools, you'll get one cohesive package, so yeah, it's probably what people want. The only exception would be, for example, if you were packaging for a distro and you want to support upgrading. In those cases, it's better for the packaging if the package version numbers match the upstream version numbers, which means separate packages.
As for the two-stepping of gcc, note that modern gcc releases have separate host and target parts of the build. You do "make all-host; make install-host" at first, which gives you the compiler but not the runtime, then you build the libraries, then go back to gcc and do "make all; make install" to do the rest. This is needed regardless of which runtime you use. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
