<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Toolchain on AllThingsEmbedded</title><link>https://allthingsembedded.com/tags/toolchain/</link><description>Recent content in Toolchain on AllThingsEmbedded</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 29 Dec 2018 17:36:13 +0000</lastBuildDate><atom:link href="https://allthingsembedded.com/tags/toolchain/index.xml" rel="self" type="application/rss+xml"/><item><title>Cross-compiling for embedded devices</title><link>https://allthingsembedded.com/2018/12/29/cross-compiling-for-embedded-devices/</link><pubDate>Sat, 29 Dec 2018 17:36:13 +0000</pubDate><guid>https://allthingsembedded.com/2018/12/29/cross-compiling-for-embedded-devices/</guid><description>&lt;p>Developing code for embedded devices is somewhat different from code for mainstream computers. One of these differences is the development environment.&lt;/p>
&lt;p>Most of the target microcontrollers or microprocessors won&amp;rsquo;t usually be suited for local development. Imagine trying to build your code on the target when the target is a simple 8-bit Microcontroller. First of all you would need a compiler for the target architecture on the target device and it would probably be extra slow and inconvenient. That is the reason behind cross-compilers (provided that the uC has enough power and memory to perform the compilation process).&lt;/p></description></item></channel></rss>