Motivation
The repository integrates a number of build tool chains, such as tools/gcc-4.8.2-Ee500v2-eabispe, tools/x86_64-apple-darwin, and tools/x86_64-unknown-linux-gnu.
The idea is to be able to build the RTOS without having to install any dependencies and to achieve reproducible builds across build hosts.
However, these build tool chains are not included in RTOS releases.
Therefore, any applications built from a release of the RTOS (as opposed to the full source code repository), rely on tool chains from the host system.
Therefore, the goals of zero-install and reproducible builds are not met for application builds from RTOS releases.
Goals
- investigate approaches to handling the above situation;
the two obvious approaches are to either drop the goals of reproducible zero-install builds or to include the build tool chains in RTOS releases.
There may be other approaches or some middle ground between these two alternatives.
- implement a suitable solution
Test Plan
Motivation
The repository integrates a number of build tool chains, such as
tools/gcc-4.8.2-Ee500v2-eabispe,tools/x86_64-apple-darwin, andtools/x86_64-unknown-linux-gnu.The idea is to be able to build the RTOS without having to install any dependencies and to achieve reproducible builds across build hosts.
However, these build tool chains are not included in RTOS releases.
Therefore, any applications built from a release of the RTOS (as opposed to the full source code repository), rely on tool chains from the host system.
Therefore, the goals of zero-install and reproducible builds are not met for application builds from RTOS releases.
Goals
the two obvious approaches are to either drop the goals of reproducible zero-install builds or to include the build tool chains in RTOS releases.
There may be other approaches or some middle ground between these two alternatives.
Test Plan