-
Notifications
You must be signed in to change notification settings - Fork 459
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
Support finding Windows tools on non-Windows host #907
Conversation
@ChrisDenton It would be great if you could give me some advice. |
e981e65
to
3162fbe
Compare
cc @thomcc I will need your help on how to move forward with this PR |
subbing. very interested to be able to use cross for msvc compilation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going through this again, I think it's ok to merge in this PR.
At the very least it shouldn't regress anything, then it will be perfectly fine for it to merge in.
If we find any issue with it lately, we could just fix it and cut a new release.
cc @cavivie Can you rebase this please? I'm willing to merge it in. |
Okay, I will do it as soon as possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
This PR contains a simple implementation of building targets on non-Windows platform. it supports manually set environment variables to find Windows msvc tools.
By setting
VCINSTALLDIR
environment variable, we can search msvc tools simply, and resolve related issues:Currently, this PR can be regarded as a draft implementation, and the implementation details may still be discussed.