Skip to content
This repository has been archived by the owner on Dec 29, 2021. It is now read-only.

main_binary should reuse the caller's target #102

Closed
epage opened this issue May 7, 2018 · 2 comments
Closed

main_binary should reuse the caller's target #102

epage opened this issue May 7, 2018 · 2 comments
Labels
bug

Comments

@epage
Copy link
Collaborator

epage commented May 7, 2018

I suspect when running cargo test --target TRIPLET that main_binary will still use the default TRIPLE.
@epage epage added the bug label May 7, 2018
@epage
Copy link
Collaborator Author

epage commented May 7, 2018

We can workaround this by having a build.rs capture the target triplet environment variable.

Example: https://github.com/mmstick/cargo-deb/blob/master/build.rs

epage added a commit to epage/assert_cli that referenced this issue May 25, 2018
@epage
fix(cargo): Run the program under correct target
e150ca1 
Unfortunately, when you explicitly call out the target, cargo does a
build distinct from the default-target build, significantly slowing own
the first test that runs.

Fixes assert-rs#102
This was referenced May 25, 2018
Closed
Closed
@epage
Copy link
Collaborator Author

epage commented May 29, 2018

The responsibility for this is moving to assert_cmd and tis will be addressed in assert-rs/assert_cmd#4

assert_cli is going to morph into a wider-focused tool, including things like assert_fs. See #41

@epage epage closed this as completed May 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@epage