-
Notifications
You must be signed in to change notification settings - Fork 114
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
Build Issues #38
Comments
that means you don't have Emscripten loaded. You need to run this command inside the emsdk folder each time you close and reopen your terminal to get it back into the path
|
I’m having the same problem here. I keep trying to do so but something about Glide64 keeps giving me errors. Honestly I think everybody would benefit from a tutorial video 😆 EDIT: Maybe I’m just stupid…? 🤔 |
@MajesticWafer what error are you getting in the terminal? I actually did a tutorial on some Emscripten basics several years back: https://www.youtube.com/watch?v=WHwl8mqVRUg&t=1673s Not sure if it's all totally applicable. I guess in my readme I assumed folks would have some basic background in emscripten, but maybe I shouldn't make that assumption. |
Funnily enough, I’m getting the same error as @LutraVibes. Then again, I don’t have much (if any) knowledge about emscripten and web assembly. I don’t, however, have much time to watch an hour video, if you know what I mean. 😢 |
@MajesticWafer @LutraVibes another thing you guys can do is create a Codespace in Github. Switch it to the devcontainer branch and click Create Codespace. I have a configuration file in that branch that will automatically give you an environment set up to build N64Wasm. Once it provisions the codespace literally all you have to do is cd into the "code" directory and run "make". it will build and copy the outputed wasm files into the dist folder. See screenshot below with the 2 red bubbles: |
@BeezBumba see above this gives you an easy way to build the n64wasm.js and n64wasm.wasm files if you don't have a dev environment set up for building the code. |
did you use the "devcontainer" branch or the "master" branch when you created the codespace? it looks like your folders are in the wrong place. like why is "dist" at the same level as "emsdk" ? if you use the devcontainer branch everything should be set up for you so you don't even need to install emscripten. |
I think I got confused. I though I had to fork the repository, then make the code space. The fork was all unnecessary. |
Yeah my codespace was also going into recovery a few times. Usually what I do when that happens is I just delete the codespace and try again after a while. Were you able to finally provision it? |
Yes I was! |
ok there is an issue with the devcontainer branch - I'm getting the same clang missing error. I will look into that. In the meantime if you are using a codespace then yeah you will need to install emscripten manually after it provisions using the instructions in the documentation. just make sure to install it in a directory outside of the N64Wasm enlistment. |
What happened here, and how do I fix it?
The text was updated successfully, but these errors were encountered: