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

fix Windows build issue #18157

Closed
wants to merge 1 commit into from
Closed

fix Windows build issue #18157

wants to merge 1 commit into from

Conversation

@tigercosmos
Copy link
Collaborator

tigercosmos commented Aug 20, 2017

It is not able to build on Windows by following README.
As AppVeyor CI use VS 2015, it seems the script is designed for VS 2015.

I try three environment:

  • Windows10 + VS2017

not work at the beginning

  • Windows10 + VS1017 with 2015 tool

PR #18145 can solve download rustc problem, but build failed.

  • Windows10 + VS2015

Work pretty well.


  • ./mach build -d does not report any errors
  • ./mach test-tidy does not report any errors
  • These changes fix #18055 (github issue number if applicable).
  • There are tests for these changes OR
  • These changes do not require tests because _____

This change is Reviewable

@highfive
Copy link

highfive commented Aug 20, 2017

Thanks for the pull request, and welcome! The Servo team is excited to review your changes, and you should hear from @cbrewster (or someone else) soon.

@tigercosmos tigercosmos mentioned this pull request Aug 20, 2017
0 of 5 tasks complete
@atouchet
Copy link
Contributor

atouchet commented Aug 20, 2017

Is #16307 an incomplete solution? I believe it should be possible to build with VS 2017.

@tigercosmos
Copy link
Collaborator Author

tigercosmos commented Aug 20, 2017

Yes, I think so. I tested in clean environment with windows10 and VS2017. Maybe need some package not mentioned in readme.

@jdm
Copy link
Member

jdm commented Aug 20, 2017

@atouchet
Copy link
Contributor

atouchet commented Aug 20, 2017

@jdm I think you mean @larsbergstrom

@larsbergstrom
Copy link
Contributor

larsbergstrom commented Aug 22, 2017

Sorry for the delay on these! I will test these on Saturday.

I would expect Servo to build cleanly in VS2015 and VS2017, largely due to the work of @UK992. The main edge cases I'd expect are trying to build within a non-cmd.exe shell (powershell, cygwin, etc.) or with some more interesting environment variables set. I'll try to dig into what's going on this weekend when I have time to sit down with it. Sorry again for the delay!

@cbrewster cbrewster assigned larsbergstrom and unassigned cbrewster Aug 23, 2017
@tigercosmos
Copy link
Collaborator Author

tigercosmos commented Aug 25, 2017

It's very weird. I try again on a new PC with VS2017 & Win10. No #18145 happens, and it works. I even not install 2015 tools. But this time I install many components (not just README mentioned). I guess some components are critical.

@larsbergstrom
Copy link
Contributor

larsbergstrom commented Aug 26, 2017

Yeah, I've confirmed on a clean machine & VM that VS 2017 is sufficient to build Servo, so I am closing this. I will look at the other issues you've raised now...

@tigercosmos
Copy link
Collaborator Author

tigercosmos commented Aug 26, 2017

@larsbergstrom Could you tell me which window10 version is used and what VS2017 components installed. I am still very confused, because in many times I have tried, I only success once, and I don't know why.

@larsbergstrom
Copy link
Contributor

larsbergstrom commented Sep 2, 2017

I'm on Windows 10 Home, version 1703, build 15063.540.

I installed Visual Studio 2017, custom installation adding Visual C++.

@tigercosmos tigercosmos deleted the tigercosmos:readme branch Sep 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

6 participants
You can’t perform that action at this time.