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'm aware of how to accomplish the cross build with cargo, but I'm not sure how to do this with bazel. There doesn't seem to be a way for me to pass my target JSON through a new rust_toolchain definition.
The text was updated successfully, but these errors were encountered:
So AFAIU the request is to add a way to pass target.json to the rust_toolchain. That's quite a simple change, and I'd say not very controversial. @davidskidmore, do you want to give creating a PR a try?
I've tried hacking something together, but haven't been able to get something working that will both accept the new json as a target and successfully use my prebuilt libraries.
I have successfully built and linked my own libraries, and created #836 to show my approach in adding support for passing a custom target specification. I can't tell if this is the "right" way, so let me know if you have any feedback.
I'm having difficulty using bazel with a custom target based on
x86_64-unknown-linux-gnu
. In theory, given a simple library:After bootstrapping libcore and friends I can now build the library for my new target:
I'm aware of how to accomplish the cross build with cargo, but I'm not sure how to do this with bazel. There doesn't seem to be a way for me to pass my target JSON through a new
rust_toolchain
definition.The text was updated successfully, but these errors were encountered: