Thanks Ben, I was just about to reply with the link: https://github.com/rust-lang/rust/pull/16156/
Cody, you are welcome to test out the branch, as you are to compile rust with OE anyway ;) On 16 Oct 2014 20:52, "Ben Harris" <m...@bharr.is> wrote: > This will be available very soon. There is a pull request in the final > stages of review that will allow you to define custom targets with custom > linkers, link args, PIC options, etc. > > That is for building binaries using rustc. I'm not sure what the solution > would be for building rustc itself. > > On 16 October 2014 12:55, Cody P Schafer <d...@codyps.com> wrote: > >> Hi all, >> >> I'm trying to create an openembedded/yocto layer that includes rust, >> and for this to work I need to be able to have rust build using target >> a compiler with a prefix that isn't included in mk/platform.mk. >> >> For example: >> >> My yocto build is targeting a beaglebone black, so an >> arm-linux-gnueabihf device. My particular gcc binary prefix is >> "arm-poky-linux-gnueabi", which isn't something that rust's build >> system knows about. >> >> >> Q: Is there an accepted way to point particular rust targets at build >> tools with a particular prefix? For example, can I tell rust's >> configure that I've got an arm-unknown-linux-gnueabihf system (which >> it understands) and then have it use tools with >> "arm-poky-linux-gnueabihf-" as their prefix? >> >> Alternately, is the current practice to have buildscripts muck with >> platform.mk to add my particular case? >> _______________________________________________ >> Rust-dev mailing list >> Rust-dev@mozilla.org >> https://mail.mozilla.org/listinfo/rust-dev >> > > > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
