-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong post-build if .cargo/config contains build target #16
Comments
Thanks for reporting! The issue is that I also encountered this underlying problem many times, e.g. as described here: rust-lang/cargo#8757 (comment). I now think the best solution for this is https://internals.rust-lang.org/t/proposal-move-some-cargo-config-settings-to-cargo-toml/13336, which would allow to specify the default target as a package-specific key in the |
Hmm, okay. Lets hope for rust-lang/cargo#9030 soon :) |
The only workaround that I'm aware of is to not use a default target and instead pass it as |
It seems to work if i remove the default target, and builds with Lines 42 to 53 in ef1b4d0
An alias like [alias]
br = "build --release --target thumbv7em-none-eabihf" Will always result in |
Have you tried including the |
Ahh, no haven't tried that. Will give it a shot EDIT |
If
.config/cargo
contains a build target wherestd
is not available, post-build will fail, as it tries to compile post-build for said target..cargo/config
:post_build.rs
:cargo post build -p factbird-rs
:I can't quite figure out if this is actually the same as #2 ?
As i see it, the post_build script should always be run using the host target, and never be influenced by
.config/cargo
target?The text was updated successfully, but these errors were encountered: