Skip to content
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

Add support for more hosts and simplify/unify host support checks #489

Merged
merged 2 commits into from
Apr 18, 2021

Conversation

alex-berger
Copy link
Contributor

This PR enables more freedom when choosing custom host/target combinations and simplifies (unifies) logic and behavior regarding when to build natively (using local toolchain) and when to use docker image based toolchain. If users explicitly passes --target ... option to cross it will always use docker image based toolchain (unless a target explicitly opts-out) and only use the local toolchain if --target option is not present.

Furthermore, no longer make any assumptions about the host, and let users use any host. It is the user's choice and responsibility to choose a working host platform and cross should not artificially limit use cases.

This PR also addresses:

@alex-berger alex-berger requested review from Dylan-DPC-zz and a team as code owners November 23, 2020 23:07
reitermarkus
reitermarkus previously approved these changes Feb 20, 2021
@reitermarkus
Copy link
Member

bors r+

bors bot added a commit that referenced this pull request Feb 20, 2021
489: Add support for more hosts and simplify/unify host support checks r=reitermarkus a=alex-berger

This PR enables more freedom when choosing custom host/target combinations and simplifies (unifies) logic and behavior regarding when to build natively (using local toolchain) and when to use docker image based toolchain. If users explicitly passes `--target ...` option to `cross` it will always use docker image based toolchain (unless a target explicitly opts-out) and only use the local toolchain if `--target` option is not present.

Furthermore, no longer make any assumptions about the host, and let users use any host. It is the user's choice and responsibility to choose a working host platform and `cross` should not artificially limit use cases.

This PR also addresses:
- [436](#436)

Co-authored-by: [email protected] <[email protected]>
@bors
Copy link
Contributor

bors bot commented Feb 20, 2021

Build failed:

…more use cases.

- Relax host check and allow any host platform.
@alex-berger
Copy link
Contributor Author

Rebased onto master and all test pass now, can we merge this into master please.

@burrbull
Copy link

bors r+

@bors
Copy link
Contributor

bors bot commented Apr 18, 2021

Build succeeded:

@bors bors bot merged commit d9ae167 into cross-rs:master Apr 18, 2021
@Emilgardis Emilgardis added this to the v0.2.2 milestone Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants