Download View/Open

Transcript
6.6. FINAL LIBRARY BUILD ARTIFACTS
6.6.1
79
Discussion
The final version of the build system for the RustyGecko platform is as standardized as we set out to achieve. This achievement ensures that the platform is easily
reusable for anyone that is familiar with the standard Cargo build process. However, there are a few deficiencies in the current design. These are related to the
discussion made in Section 9.1, but are discussed here in the context of the build
system.
The Rust project is, at the time of writing, not directly targeting the bare-metal
environment that we are considering in this thesis. As a result of this, we have to
cross-compile each of the crates in REL separately for the ARM architecture. This
process requires us to create a separate proxy project for each of the libraries that
we are using. These proxies depends on the Rust source code to be downloaded
with the rust-src project, as described in Section 6.2. This leads to duplicate
copies of the Rust source code, one for each of the crates used in REL. Another
problem with this, is the slight increase in build time introduced because the same
source code is downloaded multiple times. There have, however, been discussion
of providing an official crate for each of the libraries in RSL available on Cargo’s
package repository, which would resolve this issue.
The project layout for a RustyGecko project is not identical to that of an ordinary
Rust project. Both the ARM target specification and the linker script must currently be present in the top level directory for every project targeting RustyGecko.
We would like to provide these as part of the platform in the future, to make the
project layout identical to that of ordinary projects. This would further lower the
bar for making use of the platform in new projects.