Re: Need suggestion on GNU toolchain selection

On 2006-11-27, Michael N. Moran <mike@xxxxxxxxxxx> wrote:
FreeRTOS.org wrote:

Don't build your own!

Actually, I take exception to that. I've found it very useful
over time to learn to build the GNU/GCC toolchain from
scratch. I usually build using newlib for "bare metal"
toolchains, and crosstool is quite useful for linux/glibc
variants.

The advantage of building it yourself is that you can adapt to
new targets and toolchain upgrades. Just another notch in the
experience belt ... ymmv. Noone sait it was easy though ;-)

You really need to be able to build a toolchain yourself.

What happens when you need to incorporate a patch or use a
different version? What if you need to move to a host system
that isn't supported by your binary vendor? What if you want
to move to a target that isn't supported by your binary vendor.

If you archive the source tarballs, patches, and build script
then you aren't at the mercy of whoever you got the binary
from. You can build for any host environment. You can
incorporate any patches you need. Switching targets is also
simple.

Maybe I'm just paranoid, but after being burned by a tool
vendor once or twice, you get a little defensive.

--
Grant Edwards grante Yow! Can I have an IMPULSE
at ITEM instead?
visi.com
.

Relevant Pages