You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using xargo for a while and recently checked out cargo-xbuild. Curious as to how these work, I realised all that you need to do is build the libcore-etc for the target and put these in the sysroot directory. Rustup manages its own sysroot for common targets.
It would be really nice if we could instead do rustup target add x86_64-sel4-robigalia.json to ask rustup to track the target file and rebuild the libcore-etc when either rustc updates or when the user attempts to build something using the target with a newer rustc or when the target file changes.
As a bonus feature it might be faster (or bandwidth-cheaper or just more convenient such as when offline) for some people to build any simple targets using only rust-src and a collection of target.json files.
I'm currently just using unmodified and unwrapped cargo with only these two environment variables set after having used xargo/xbuild at least once after calling rustup update.
As I understand it the developers intend to fold cargo-xbuild's functionality into Cargo itself (rust-lang/cargo#4959) but progress stalled for the duration of Rust 2018's impl period because the embedded WG ended up only needing a small number of new targets rather than a general solution for compiling the standard library for arbitrary targets.
Hello.
I've been using
xargo
for a while and recently checked outcargo-xbuild
. Curious as to how these work, I realised all that you need to do is build the libcore-etc for the target and put these in the sysroot directory. Rustup manages its own sysroot for common targets.It would be really nice if we could instead do
rustup target add x86_64-sel4-robigalia.json
to ask rustup to track the target file and rebuild the libcore-etc when either rustc updates or when the user attempts to build something using the target with a newer rustc or when the target file changes.As a bonus feature it might be faster (or bandwidth-cheaper or just more convenient such as when offline) for some people to build any simple targets using only
rust-src
and a collection oftarget.json
files.I'm currently just using unmodified and unwrapped cargo with only these two environment variables set after having used xargo/xbuild at least once after calling
rustup update
.The text was updated successfully, but these errors were encountered: