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

emsdk_env not working in powershell #5086

Open
1993hzh opened this issue Mar 27, 2017 · 4 comments
Open

emsdk_env not working in powershell #5086

1993hzh opened this issue Mar 27, 2017 · 4 comments

Comments

@1993hzh
Copy link

1993hzh commented Mar 27, 2017

I am using this in Windows10, I followed the steps like http://webassembly.org/getting-started/developers-guide/, everything went on well until set emsdk_env.

The emsdk_env works well in cmd but not in powershell. When I am using powsershell to run emsdk_env, no error occurred but the environment vars just do not work properly, for example
env | grep path
does not contain directories added by script.

I am not sure whether emsdk_env support powershell or not, could you please help take a look?

@stale
Copy link

stale bot commented Aug 30, 2019

This issue has been automatically marked as stale because there has been no activity in the past 2 years. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant.

@stale stale bot added the wontfix label Aug 30, 2019
@stale stale bot closed this as completed Sep 6, 2019
@yikescloud
Copy link

Confirm this when I try to build godot using emsdk, the powershell env set not work but cmd is fine

@sbc100 sbc100 reopened this Nov 7, 2023
@stale stale bot removed the wontfix label Nov 7, 2023
@sbc100
Copy link
Collaborator

sbc100 commented Nov 7, 2023

We do have some powershell tests in emsdk so we know it works in come configurations at least.

Can you show the emsdk_env command you ran and its output?

@RReverser
Copy link
Collaborator

FWIW I'm also using emsdk_env from PowerShell successfully all the time. The most likely culprit is someone accidentally uses ...\emsdk_env.bat instead of just ...\emsdk_env or ...\emsdk_env.ps1.

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

No branches or pull requests

4 participants