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

An alternative solution to build on Windows #18256

Closed
tigercosmos opened this issue Aug 26, 2017 · 5 comments
Closed

An alternative solution to build on Windows #18256

tigercosmos opened this issue Aug 26, 2017 · 5 comments

Comments

@tigercosmos
Copy link
Collaborator

@tigercosmos tigercosmos commented Aug 26, 2017

As #18055 happens, I am still not able to build followed by README. Although @larsbergstrom tested it works as #18157, but I always test failed. I try to debug, but no progress.

I find an alternative solution to build on windows, and it works. I think it is worth to share, and let other developers who encountering problems while building have a new way.

Here's the steps:

  1. Download and install Build Tools for Visual Studio 2017
  2. Install python2.7 x86-x64 and virtualenv
  3. Since mach.bat cannot find the prompt, we should execute Developer Command Prompt for VS 2017 manually in the Windows menu.
  4. cd to/the/path/servo
  5. python mach build -d
@tigercosmos
Copy link
Collaborator Author

@tigercosmos tigercosmos commented Aug 27, 2017

If get error about rustc by unknown, #18145 can fix.

@shinglyu
Copy link
Member

@shinglyu shinglyu commented Aug 28, 2017

So the main difference you are proposing is step 3 to 5? If so (and if it's not possible to fix the vs shell anytime soon) I think it's worth adding a troubleshooting sub-section under the window build section in the README. Nice job finding an workaround.

@tigercosmos
Copy link
Collaborator Author

@tigercosmos tigercosmos commented Aug 28, 2017

@shinglyu Step 1 is also different. Instead of installing VS 2017 IDE, I install VS 2017 tool only.

@tigercosmos tigercosmos mentioned this issue Aug 29, 2017
1 of 5 tasks complete
@larsbergstrom
Copy link
Contributor

@larsbergstrom larsbergstrom commented Sep 2, 2017

The work that @UK992 should have made it so that we work with the VS tools only and do not need Developer Command Prompt for VS 2017. @UK992 Do you have any opinions / ideas on this?

@tigercosmos
Copy link
Collaborator Author

@tigercosmos tigercosmos commented Sep 2, 2017

But if I only install VS tool 2017, use cmd run mach.bat get

C:\Users\Tiger\Desktop\servo>mach.bat run
Visual Studio 2015 or 2017 is not installed.
Download and install Visual Studio 2015 or 2017 from https://www.visualstudio.com/

I guess mach.bat should be modified.

@tigercosmos tigercosmos closed this Sep 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

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