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
Both the Travis-CI and AppVeyor configs pass --target $TARGET/--target %TARGET% flags to cargo when building and testing. Why is this? Would it make any difference if they were removed?
At least for AppVeyor the host in the %TARGET% variable has already been configured as the default in:
The reason I ask is because of this bug: rust-lang/cargo#4254
Which stops me from using the serde features = ["derive"] trick on stable Rust on Windows. So I'm thinking to remove --target from my appveyor.yml. It seems to work, just want to check if there are any factors I miss.
The text was updated successfully, but these errors were encountered:
faern
changed the title
Why is --target passed when it's already the default toolchain?
Why is --target passed when it's already the default toolchain?
Oct 13, 2017
Both the Travis-CI and AppVeyor configs pass
--target $TARGET
/--target %TARGET%
flags tocargo
when building and testing. Why is this? Would it make any difference if they were removed?At least for AppVeyor the host in the
%TARGET%
variable has already been configured as the default in:The reason I ask is because of this bug: rust-lang/cargo#4254
Which stops me from using the serde
features = ["derive"]
trick on stable Rust on Windows. So I'm thinking to remove--target
from myappveyor.yml
. It seems to work, just want to check if there are any factors I miss.The text was updated successfully, but these errors were encountered: