-
Notifications
You must be signed in to change notification settings - Fork 0
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
questions #2
Comments
"open it in your browser" wasn't intended to be a literal shell command. The way I tend to do it personally is by typing the URL in my browser's location field. Not if 1) you already have an environment that's most of the way there, 2) you don't mind changing it, and 3) only don't have any problems on any other machines you use. Different environments can be more or less easy to prepare, and lots of people don't like globally installing things that change their environments. The Vagrant approach keeps the dev environment isolated and exactly replicates it on every work machine, so regardless of whether you're using a Mac desktop, a Linux laptop, or an MS-Win tablet you get something that works the same and is trivial to remove. |
thanks! |
ok, all I had to do was add this: nim.cfg
in Samples/ and then this fixes #1 as well as this issue (for me...) ; and maybe even #3 /cc @AchalaSB |
in https://www.spiria.com/en/blog/web-applications/webassembly-nim what worked for me was
(for eg)
python -m SimpleHTTPServer 9009 && open http://localhost:9009/hello.html
instead ofopen hello.html
( as seems to be suggested inand open it in your browser.
)on OSX, with C++, I can run emscripten locally and run a wasm hello world demo without having to use vagrant and ssh to a VM; is there a fundamental reason why we need vagrant for nim ?
The text was updated successfully, but these errors were encountered: