you were right, I found the .emscripten file and it was in my C:\Users\yunzh directory. For some reason I kept looking for a folder and didn’t see the file was right there. I’ll take a deeper look into how it got there in the first place.
I was able to get the following result by setting $env:Home instead of $env:UserProfile
~ $ emcc -v
==============================================================================
Welcome to Emscripten!
This is the first time any of the Emscripten tools has been run.
A settings file has been copied to ~/.emscripten, at absolute path: D:\Applications\Epic Games\4.12\Engine\Intermediate\Build\HTML5/.emscripten
It contains our best guesses for the important paths, which are:
LLVM_ROOT = D:\Applications\Epic Games\4.12\Engine\Source\ThirdParty\HTML5\emsdk\Win64\clang\e1.35.0_64bit
NODE_JS = D:\Applications\Epic Games\4.12\Engine\Source\ThirdParty\HTML5\emsdk\Win64\node\4.1.1_64bit\bin\node.exe
EMSCRIPTEN_ROOT = D:\Applications\Epic Games\4.12\Engine\Source\ThirdParty\HTML5\emsdk\emscripten\1.35.0
Please edit the file if any of those are incorrect.
This command will now exit. When you are done editing those paths, re-run it.
==============================================================================
However upon launch, the file becomes “.emscripten.save” and I get the same error again
interesting - that shouldn’t be usable on windows. but it will be easy to add to all platforms (i.e. windows, mac and linux) while also setting userprofile for windows. it wont hurt with the extra environment variable settings. i’ll have that in for 4.14.
I try to package my game that use github master branch(4.14 and 4.15) and the error indicate Engine\Intermediate\Build\HTML5.emscripten didn’t generated.
This bug happens when I try to use command line, but it works fine on when I use editor to do the package.
I pulled down the Master Branch myself and I was not able to reproduce this issue. Please keep in mind that the Master Branch is more likely to have bugs in it as it’s not a release branch. Please try this again in 4.13.1. If you run into this issue there, please submit a new question and link back to this one.
I found the root cause for my scenario. I’m using scoop which is a very nice linux styled package manager for Windows Powershell. But the openssh package was setting $HOME env var which causes the various issues I’ve experienced above. After removing the line that sets the env var I no longer get this issue.
interesting, this is a second case (that i know of) that’s causing problems with this… i will look at this issue on our side to see what can be done to help fix this problem. note: this may not get looked at until 4.17 (i’m busy with 4.16 bugs). please stand by…