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

Update How-to-Contribute.md #40

Closed
wants to merge 1 commit into from
Closed

Conversation

sgharms
Copy link

@sgharms sgharms commented Nov 28, 2017

Document the process to get the toolchain up and running in WSL, but also document that it, sadly, will be for naught.

@sgharms
Copy link
Author

sgharms commented Nov 30, 2017

Documentation change supported by microsoft/WSL#2293 via microsoft/vscode#39286 (comment)

@cwegener
Copy link

cwegener commented Dec 2, 2017

Let me start by apologizing for hijacking this issue.

I am new to vscode and I saw the issue that you created in the vscode repo about 'building' vscode.

I have been searching high and low through the vscode repository, but I can't for the life of me find any build or run instructions for vscode at all.

I also cloned the 'vscode-wiki' repository but I can't find any instructions on building vscode in here either.

Would you be able to point to the documentation (if any). From your issue that you raised, it seems like you may have some information on how to build and run vscode.

Thanks.

@cwegener
Copy link

cwegener commented Dec 2, 2017

Never mind. I think I just found the markdown file in the vscode-repo! ( ./How-to-Contribute.md )

@Tyriar
Copy link
Member

Tyriar commented Dec 11, 2017

I'm not sure this is the right place to call this out since the real underlying problem here is that you cannot launch the Linux version of VS Code via WSL. A simpler "Building and debugging via WSL is not supported" under the Windows section would be better imo as the page is already quite long.

1. Document that WSL built / run of VSCode is not
   functional
2. Provide link to a master issue in the WSL
   repository where the behavior that inhibits
   Node thus Electron, thus VSCode, can be tracked
   for those who believe they can get it working
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.

3 participants