Support multiple targets

[mcandre]

Allow users to specify multiple targets, such as both x86_64-unknown-linux-gnu and x86_64-unknown-linux-musl, so that cargo build produces both artifacts.

By the way, how will the filename paths differentiate between multiple targets? Gox allows the target metadata to appear in the destination filepath, for example.

[alexcrichton]

Sounds like a reasonable feature to implement to me! I think the backend of Cargo isn't quite read to do this kind of operation, but with a small amount of refactoring it should be able to, namely parameterizing Kind to have more than one kind of Target.

[steveklabnik]

I'm hitting this today; I am writing a client and server both in wasm. Client crate needs to be compiled with one target, the server with another.

[michaeleiselsc]

if we did this, would it be possible to generate the IR only once but build for multiple backends?

[sfackler]

No, IR is platform dependent.

…

On Tue, Mar 20, 2018 at 5:10 AM Michael Eisel ***@***.***> wrote: if we did this, would it be possible to generate the IR only once but build for multiple backends? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3913 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABY2UfG0YeoM5qyKY9LVEyXhD5TOvrKKks5tgI9IgaJpZM4M5MzS> .

[dwijnand]

What does cargo::ops::cargo_rustc::Kind denote?

[ehuss]

What does cargo::ops::cargo_rustc::Kind denote?

Kind was moved here. Host is used for proc-macros, plugins, and build scripts which must be compiled for the host architecture. Target is used when the user specifies --target.

[ehuss]

Closing in favor of tracking issue #8176.