Web exports guide #15

Esption · 2023-11-27T23:10:16Z

Not sure about the markdown formatting and such, but otherwise I'm happy with this. Hoping to get something out there to start some discussion/suggestions.

PgBiel

Great job! Thanks for bringing everything together, it's looking great. 👍

Mostly nitpicks incoming now. 😄

PgBiel · 2023-11-28T00:12:10Z

src/toolchain/web-guide.md

+
+# Intro to Web Builds
+
+Web builds are a fair bit more to get started with compared to native builds.


I think this might sound a bit more natural:

Suggested change

Web builds are a fair bit more to get started with compared to native builds.

Web builds are a fair bit more difficult to get started with compared to native builds.

PgBiel · 2023-11-28T00:13:25Z

src/toolchain/web-guide.md

+# Intro to Web Builds
+
+Web builds are a fair bit more to get started with compared to native builds.
+This will be a complete guide on how to get things compiled.


Just to be a bit more descriptive:

Suggested change

This will be a complete guide on how to get things compiled.

This will be a complete guide on how to properly compile your game using `gdext` to WebAssembly, which will allow you to use `gdext` in the web.

I agree with the extension, but I think "properly" is not needed 😉

I agree! Feel free to remove "properly"

PgBiel · 2023-11-28T00:14:46Z

src/toolchain/web-guide.md

+
+Web builds are a fair bit more to get started with compared to native builds.
+This will be a complete guide on how to get things compiled.
+Setting up a web server is out-of-scope for this guide, and best found elsewhere.


Being a bit more precise (also I think no hyphens are needed here):

Suggested change

Setting up a web server is out-of-scope for this guide, and best found elsewhere.

Setting up a web server to host your game in is out of scope for this guide, and is best explained elsewhere.

PgBiel · 2023-11-28T00:15:51Z

src/toolchain/web-guide.md

+This will be a complete guide on how to get things compiled.
+Setting up a web server is out-of-scope for this guide, and best found elsewhere.
+
+- Web support with `gdext` is experimental and should be understood as such before proceeding.


Do the gdext docs have support for warning boxes? I believe that'd be ideal here. Otherwise, we could add something in bold like WARNING:.

Also, I think it may be interesting to point out explicitly here that it "may have bugs we aren't aware of".

I believe you'll get a compile error if you don't enable the experimental-wasm feature flag. Beyond that I'm not sure.

We do have warning boxes, see ```admonish tags elsewhere.

But only the 2nd bullet point is a warning. The first can also be moved up to the "This will be a complete guide..." section.

PgBiel · 2023-11-28T00:16:25Z

src/toolchain/web-guide.md

+## Installing Pre-Requisites
+
+- Install a nightly build of `rustc`, the `wasm32-unknown-emscripten` target for `rustc`, and `rust-src`.
+Assuming that Rust was installed with rustup, this is quite simple.


For consistency:

Suggested change

Assuming that Rust was installed with rustup, this is quite simple.

Assuming that Rust was installed with `rustup`, this is quite simple.

PgBiel · 2023-11-28T00:38:54Z

src/toolchain/web-guide.md

+- Edit the project's `.gdextension` to include the web path.
+  This is probably at `godot/EXTENSIONNAME.gdextension`.
+  The format will be similar to the following


Clearer (what is the "web path"?)

Suggested change

- Edit the project's `.gdextension` to include the web path.

This is probably at `godot/EXTENSIONNAME.gdextension`.

The format will be similar to the following

- Edit the project's `.gdextension` file to include the path to the compiled WASM binary.

The file to edit will probably be at `godot/EXTENSIONNAME.gdextension`.

The format will be similar to the following

PgBiel · 2023-11-28T00:39:44Z

src/toolchain/web-guide.md

+  ```
+
+- Compile the code.
+  It is necessary to both use the nightly compiler and specify to build std[^3], along with specifying the emscripten target.


Gotta check if the monospace doesn't break the footnote, but I believe it shouldn't

Suggested change

It is necessary to both use the nightly compiler and specify to build std[^3], along with specifying the emscripten target.

It is necessary to both use the nightly compiler and specify to build `std`[^3], along with specifying the Emscripten target.

PgBiel · 2023-11-28T00:40:10Z

src/toolchain/web-guide.md

+  cargo +nightly build -Zbuild-std --target wasm32-unknown-emscripten
+  ```
+
+[^3]: The primary reason for this is it's necessary to compile with `-sSHARED_MEMORY` enabled, but the shipped `std` is not, so building std is a requirement. Related info on about wasm support can be found [here](https://github.com/rust-lang/rust/issues/77839).


Consistency and other things

Suggested change

[^3]: The primary reason for this is it's necessary to compile with `-sSHARED_MEMORY` enabled, but the shipped `std` is not, so building std is a requirement. Related info on about wasm support can be found [here](https://github.com/rust-lang/rust/issues/77839).

[^3]: The primary reason for this is it's necessary to compile with `-sSHARED_MEMORY` enabled, which the shipped `std` doesn't, so building `std` is a requirement. Related info on WASM support can be found [here](https://github.com/rust-lang/rust/issues/77839).

PgBiel · 2023-11-28T00:44:08Z

src/toolchain/web-guide.md

+- Back from the main editor screen, there's an option to run the web debug build without needing to do an export or set up a web server.
+  At the top-right, choose `Remote Debug > Run in Browser` and it will automatically open up a web browser.
+  If your default browser is not Chrome or Edge, you'll need to copy the URL and paste it into one.[^4]
+  ![Location of built-in web server](images/web-browser_run.png)


Suggested change

- Back from the main editor screen, there's an option to run the web debug build without needing to do an export or set up a web server.

At the top-right, choose `Remote Debug > Run in Browser` and it will automatically open up a web browser.

If your default browser is not Chrome or Edge, you'll need to copy the URL and paste it into one.[^4]

![Location of built-in web server](images/web-browser_run.png)

- Back to the main editor screen, there's an option to run the web debug build (_not_ release) locally without needing to fully export the game or set up a web server.

At the top right, choose `Remote Debug > Run in Browser` and it will automatically open up a web browser.

If your default browser is not Chromium-based (e.g. if you use Firefox or Safari, currently unsupported), you'll need to copy the URL (which is usually at `localhost:8060`) and open it in a supported browser, such as Chrome or Edge.[^4]

![Location of built-in web server](images/web-browser_run.png)

PgBiel · 2023-11-28T00:45:17Z

src/toolchain/web-guide.md

+- Currently the only option for wasm debugging is
+  [This extension](https://chromewebstore.google.com/detail/cc++-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb?pli=1)
+  for Chrome. It adds support for breakpoints and a memory viewer into the F12 menu.


Consistency etc.

Suggested change

- Currently the only option for wasm debugging is

[This extension](https://chromewebstore.google.com/detail/cc++-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb?pli=1)

for Chrome. It adds support for breakpoints and a memory viewer into the F12 menu.

- Currently the only option for WASM debugging is

[this extension](https://chromewebstore.google.com/detail/cc++-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb?pli=1)

for Chrome. It adds support for breakpoints and a memory viewer into the F12 menu.

Bromeon

Thanks a lot, this is a great write-up! 👍
Much more in detail than my short list 😅

Do you also want to mention the dodge-the-creeps example, which is somewhat prepared already?

The entire page is now consisting of bullet points, I don't think this is necessary. Tutorial style guides have continuous flow, so I think you could de-dent most text and use regular prose.

Unordered bullet lists can be used in places where you explain multiple things, but their order doesn't really matter. Ordered lists can be used when order matters or you later want to refer back to a certain point, e.g. you analyze a code snippet and explain the symbols occurring in order of appearance in code. But I wouldn't generally use lists for tutorial steps (as the whole book is such). See also Hello World page.

Bromeon · 2023-11-28T07:29:13Z

src/SUMMARY.md

@@ -15,6 +15,7 @@
  - [Compatibility and stability](toolchain/compatibility.md)
  - [Selecting a Godot version](toolchain/godot-version.md)
  - [Debugging](toolchain/debugging.md)
+  - [Web Target Guide](toolchain/web-guide.md)


Suggested change

- [Web Target Guide](toolchain/web-guide.md)

- [Export to Web](toolchain/export-web.md)

Bromeon · 2023-11-28T07:30:23Z

src/toolchain/web-guide.md

+# Intro to Web Builds
+
+Web builds are a fair bit more to get started with compared to native builds.
+This will be a complete guide on how to get things compiled.


I agree with the extension, but I think "properly" is not needed 😉

Bromeon · 2023-11-28T07:32:08Z

src/toolchain/web-guide.md

+This will be a complete guide on how to get things compiled.
+Setting up a web server is out-of-scope for this guide, and best found elsewhere.
+
+- Web support with `gdext` is experimental and should be understood as such before proceeding.


We do have warning boxes, see ```admonish tags elsewhere.

But only the 2nd bullet point is a warning. The first can also be moved up to the "This will be a complete guide..." section.

Bromeon · 2023-11-28T07:35:19Z

src/toolchain/web-guide.md

+- Install a nightly build of `rustc`, the `wasm32-unknown-emscripten` target for `rustc`, and `rust-src`.
+Assuming that Rust was installed with `rustup`, this is quite simple.


Maybe add that nightly is needed for the build flag -Zbuild-std.

Bromeon · 2023-11-28T07:35:53Z

src/toolchain/web-guide.md

+
+  ```sh
+  rustup toolchain install nightly
+  rustup component add rust-src --toolchain nightly


Is this 2nd step really needed? AFAIR I never did this.

See here: https://discord.com/channels/723850269347283004/1134478713002655876/1176743545768521738

It wasn't necessary for me, but someone in the discord somehow didn't have rust-src. So, I think best to leave it there as a just in case? Shouldn't do anything if it's already installed, at least.

Yea I was installing everything from scratch in a Linux VM and rustup didn't seem to install it by default.

You're right, it looks like it's required:

rust-src — This is a local copy of the source code of the Rust standard library. This can be used by some tools, such as RLS, to provide auto-completion for functions within the standard library; Miri which is a Rust interpreter; and Cargo's experimental build-std feature, which allows you to rebuild the standard library locally.

Bromeon · 2023-11-28T07:39:21Z

src/toolchain/web-guide.md

+  ```
+
+- At the same level as your `Cargo.toml`, create a `.config` directory and inside of that,
+  create a `config.toml` file (if one doesn't already exist). The contents of this file should be as follows


Suggested change

create a `config.toml` file (if one doesn't already exist). The contents of this file should be as follows

create a `config.toml` file (if one doesn't already exist). The contents of this file should be as follows:

Bromeon · 2023-11-28T07:41:34Z

src/toolchain/web-guide.md

+  ```
+
+- Edit the project's `.gdextension` file to include support for web exports.
+  This file will probably be at `godot/EXTENSIONNAME.gdextension`.


Suggested change

This file will probably be at `godot/EXTENSIONNAME.gdextension`.

This file will probably be at `godot/{YourCrate}.gdextension`.

to be consistent with Hello World.

Bromeon · 2023-11-28T07:41:47Z

src/toolchain/web-guide.md

+
+- Edit the project's `.gdextension` file to include support for web exports.
+  This file will probably be at `godot/EXTENSIONNAME.gdextension`.
+  The format will be similar to the following


Suggested change

The format will be similar to the following

The format will be similar to the following:

Bromeon · 2023-11-28T07:44:40Z

src/toolchain/web-guide.md

+---
+
+
+## **KNOWN CAVEATS**


I would not use SCREAMING CASE here.

Suggested change

## **KNOWN CAVEATS**

## Known caveats

Or alternatively, an ```admonish warning title="Known caveats" box.

Bromeon · 2023-11-28T07:51:45Z

src/toolchain/images/web-browser_run.png

should be named web-browser-run.png (dashes)

Bromeon · 2023-11-28T07:55:55Z

src/toolchain/web-guide.md

+---
+
+
+## Set up and Test in the Godot Editor


Suggested change

## Set up and Test in the Godot Editor

## Godot Editor setup

Esption · 2023-11-28T22:45:15Z

Thanks @Bromeon, didn't know about admonish stuff before :) Hopefully all is well, and I can squash to a single commit then.

PgBiel · 2023-11-28T22:58:40Z

src/toolchain/export-web.md

+godot = { git = "https://github.com/godot-rust/gdext", branch = "master", features = ["experimental-wasm", "lazy-function-tables"] }
+```
+
+At the same level as your `Cargo.toml`, create a `.config` directory and inside of that,


Edit: turns out I had already suggested this above, sorry lol
Keeping this here anyway for future reference :p

Suggested change

At the same level as your `Cargo.toml`, create a `.config` directory and inside of that,

At the same level as your `Cargo.toml`, create a `.cargo` directory and, inside of that,

Bromeon

Rendered it now and found a few more things 😉 the footnotes are great, thanks a lot for the thorough descriptions and external links!

In this repo, no need to squash in a single commit, I can do squash-on-merge.

Bromeon · 2023-11-29T19:10:32Z

src/toolchain/export-web.md

+This will be a complete guide on how to get things compiled.
+However, setting up a web server to host and share your game is considered out of scope of this guide, and is best explained elsewhere.
+
+Information to consider before starting:


This should no longer be necessary, the yellow warning box draws enough attention.

Yes, only this part:

Information to consider before starting:

Bromeon · 2023-11-29T19:10:42Z

src/toolchain/export-web.md

+---
+
+
+## Installing Pre-Requisites


Suggested change

## Installing Pre-Requisites

## Installing pre-requisites

Bromeon · 2023-11-29T19:13:14Z

src/toolchain/export-web.md

+## Installing Pre-Requisites
+
+Install a nightly build of `rustc`, the `wasm32-unknown-emscripten` target for `rustc`, and `rust-src`.
+The reason that a nightly `rustc` is required is that nightly is required to build `std` (`-Zbuild-std`).


Suggested change

The reason that a nightly `rustc` is required is that nightly is required to build `std` (`-Zbuild-std`).

The reason why nightly `rustc` is required is the unstable flag to build `std` ([`-Zbuild-std`][flag-build-std]).

With

[flag-build-std]: https://doc.rust-lang.org/cargo/reference/unstable.html#list-of-unstable-features

Bromeon · 2023-11-29T19:14:51Z

src/toolchain/export-web.md

+  rustup target add wasm32-unknown-emscripten --toolchain nightly
+  ```
+
+Next, install Emscripten.  The simplest way to achieve this is to install `emsdk` from the git repo. Recommended to use version 3.1.39 for now[^1]


Suggested change

Next, install Emscripten. The simplest way to achieve this is to install `emsdk` from the git repo. Recommended to use version 3.1.39 for now[^1]

Next, install Emscripten. The simplest way to achieve this is to install [`emsdk` from the git repo][emsdk-git].

We recommend version 3.1.39 for now.[^1]

with:

[emsdk-git]: https://github.com/emscripten-core/emsdk#readme

(also added trailing full-stop).

Bromeon · 2023-11-29T19:16:25Z

src/toolchain/export-web.md

+source ./emsdk.sh     (or ./emsdk.bat on windows)
+```
+
+It would also be HIGHLY recommended to follow the instructions in the terminal to add `emcc`[^2] to your `PATH`.


Suggested change

It would also be HIGHLY recommended to follow the instructions in the terminal to add `emcc`[^2] to your `PATH`.

It would also be **highly** recommended to follow the instructions in the terminal to add `emcc`[^2] to your `PATH`.

Bromeon · 2023-11-29T19:22:41Z

src/toolchain/export-web.md

+- Create a `.cargo` directory at the same level as your `Cargo.toml`.
+- Inside of that directory, create a `config.toml` file.
+
+The contents of this file need to contain the following:


Suggested change

The contents of this file need to contain the following:

This file needs to contain the following:

Bromeon · 2023-11-29T19:25:15Z

src/toolchain/web-guide.md

+  [target.wasm32-unknown-emscripten]
+  rustflags = [
+      "-C", "link-args=-sSIDE_MODULE=2",
+      "-C", "link-args=-sUSE_PTHREADS=1",


Is the new flag already supported on our suggested minimum version?

If yes, I don't see any reason to keep the deprecated one around.

If no, we should use the deprecated one with a comment, that in newer Emscripten versions, a different flag is used.

Bromeon · 2023-11-29T19:27:25Z

src/toolchain/export-web.md

+web.debug.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/debug/EXTENSIONNAME.wasm"
+web.release.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/release/EXTENSIONNAME.wasm"


Suggested change

web.debug.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/debug/EXTENSIONNAME.wasm"

web.release.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/release/EXTENSIONNAME.wasm"

...

[libraries]

...

web.debug.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/debug/EXTENSIONNAME.wasm"

web.release.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/release/EXTENSIONNAME.wasm"

Also, would you need to replace EXTENSIONNAME with {YourCrate} here?

Not sure about the flag! Actually didn't notice that I had an older one on my personal config file.

Bromeon · 2023-11-29T19:29:03Z

src/toolchain/export-web.md

+This file will probably be at `godot/{YourCrate}.gdextension`.
+The format will be similar to the following:
+
+```gdextension


Using ```ini here would at least provide some syntax highlighting.

Bromeon · 2023-11-29T19:31:38Z

src/toolchain/export-web.md

+Add a web export in the Godot Editor. In the top menu bar, go to `Project > Export...` and configure it there.
+Make sure to turn on the `Extensions Support` checkbox.


Should we mention to download export templates if they are not yet configured?

I think you get a prompt if it's missing to download it, and should be downloaded at the same time you'd download templates for any other export. I'd have to intentionally trigger that and see about that.

From the last time I tried it in my VM, I believe the Export window displays some red text at the bottom suggesting you need Export Templates, but I think you still need to click some buttons to prompt the download. Could be useful to list the steps needed, but very briefly.

I see. It's fine to not explicitly mention it then.

Bromeon · 2023-11-29T22:19:07Z

src/toolchain/export-web.md

+Add a web export in the Godot Editor. In the top menu bar, go to `Project > Export...` and configure it there.
+Make sure to turn on the `Extensions Support` checkbox.


I see. It's fine to not explicitly mention it then.

Bromeon · 2023-11-29T22:21:06Z

src/toolchain/export-web.md

+[target.wasm32-unknown-emscripten]
+rustflags = [
+    "-C", "link-args=-sSIDE_MODULE=2",
+    "-C", "link-args=-pthread",


Thanks for changing this!
Sorry I wasn't very clear before, maybe I'd still mention the old one just in case someone is used to that (otherwise they might wonder where it is).

That is:

Suggested change

"-C", "link-args=-pthread",

"-C", "link-args=-pthread", # was -sUSE_PTHREADS=1 in earlier versions

What part not to mention? Sorry. If you mean line 112 then... that's kinda confusing. I can remove the images about the error for missing templates, I guess. They don't really add much besides push the page length; it feels like anyway.

Just apply my suggestion here, so that people familiar with the old flag aren't confused 🙂

I can remove the images about the error for missing templates, I guess. They don't really add much besides push the page length; it feels like anyway.

Yeah, would be good to focus more on the WASM topic, you can remove them.

Bromeon

Thanks! I marked some pending comments, so they're not overlooked.

After the web-missing-template.png is removed, there's still web-export.png which is 168 kB. Do you think it's possible to reduce the size without losing quality?

Bromeon · 2023-12-06T14:21:10Z

src/toolchain/export-web.md

+---
+
+
+## Installing Pre-Requisites


Bromeon · 2023-12-06T14:21:42Z

src/toolchain/export-web.md

+It is likely to due a bug, but is still being investigated.  Edit the line to something like the following:
+
+```toml
+godot = { git = "https://github.com/godot-rust/gdext", branch = "master", features = ["experimental-wasm", "lazy-function-tables"] }


Bromeon · 2023-12-06T14:21:45Z

src/toolchain/export-web.md

+godot = { git = "https://github.com/godot-rust/gdext", branch = "master", features = ["experimental-wasm", "lazy-function-tables"] }
+```
+
+If you do not already have `.cargo/config.toml` file, do the following:


Bromeon · 2023-12-06T14:22:30Z

src/toolchain/export-web.md

+[target.wasm32-unknown-emscripten]
+rustflags = [
+    "-C", "link-args=-sSIDE_MODULE=2",
+    "-C", "link-args=-pthread",


Just apply my suggestion here, so that people familiar with the old flag aren't confused 🙂

I can remove the images about the error for missing templates, I guess. They don't really add much besides push the page length; it feels like anyway.

Yeah, would be good to focus more on the WASM topic, you can remove them.

Bromeon · 2023-12-06T14:25:21Z

src/toolchain/export-web.md

+[this extension](https://chromewebstore.google.com/detail/cc++-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb?pli=1)
+for Chrome. It adds support for breakpoints and a memory viewer into the F12 menu.
+
+---


Still a horizontal line 😉

Bromeon · 2023-12-06T14:26:58Z

src/toolchain/export-web.md

+## Debugging
+
+Currently the only option for WASM debugging is
+[this extension](https://chromewebstore.google.com/detail/cc++-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb?pli=1)


Could you add the name of the extension in the link text, and use the [<name of extension>][wasm-debugger] format (i.e. move the actual link to the end of the section)?

Bromeon · 2023-12-12T18:48:43Z

Addressed the last few remarks, reduced PNG size and linked to Godot export tutorial in place of troubleshooting images.

Thanks a lot for this great addition and everyone that contributed to it, especially @Esption for enduring the tough review! 🚀

PgBiel reviewed Nov 28, 2023

View reviewed changes

Bromeon reviewed Nov 28, 2023

View reviewed changes

PgBiel reviewed Nov 28, 2023

View reviewed changes

Bromeon reviewed Nov 29, 2023

View reviewed changes

Bromeon reviewed Dec 6, 2023

View reviewed changes

Bromeon added the new-topic New content added to the book label Dec 6, 2023

Bromeon force-pushed the master branch from 3010c34 to 7bd01db Compare December 12, 2023 18:38

Esption and others added 2 commits December 12, 2023 19:41

Draft for web exports guide

539391d

Allow <br> tags, enforce --- hr style

84fb6d3

Bromeon force-pushed the master branch from 7bd01db to 84fb6d3 Compare December 12, 2023 18:41

Bromeon merged commit 87145ce into godot-rust:master Dec 12, 2023
3 checks passed


		# Intro to Web Builds

		Web builds are a fair bit more to get started with compared to native builds.

	Web builds are a fair bit more to get started with compared to native builds.
	Web builds are a fair bit more difficult to get started with compared to native builds.

	This will be a complete guide on how to get things compiled.
	This will be a complete guide on how to properly compile your game using `gdext` to WebAssembly, which will allow you to use `gdext` in the web.

	Setting up a web server is out-of-scope for this guide, and best found elsewhere.
	Setting up a web server to host your game in is out of scope for this guide, and is best explained elsewhere.

	Assuming that Rust was installed with rustup, this is quite simple.
	Assuming that Rust was installed with `rustup`, this is quite simple.

	It is necessary to both use the nightly compiler and specify to build std[^3], along with specifying the emscripten target.
	It is necessary to both use the nightly compiler and specify to build `std`[^3], along with specifying the Emscripten target.

	[^3]: The primary reason for this is it's necessary to compile with `-sSHARED_MEMORY` enabled, but the shipped `std` is not, so building std is a requirement. Related info on about wasm support can be found [here](https://github.com/rust-lang/rust/issues/77839).
	[^3]: The primary reason for this is it's necessary to compile with `-sSHARED_MEMORY` enabled, which the shipped `std` doesn't, so building `std` is a requirement. Related info on WASM support can be found [here](https://github.com/rust-lang/rust/issues/77839).

	- [Web Target Guide](toolchain/web-guide.md)
	- [Export to Web](toolchain/export-web.md)

		- Install a nightly build of `rustc`, the `wasm32-unknown-emscripten` target for `rustc`, and `rust-src`.
		Assuming that Rust was installed with `rustup`, this is quite simple.

	create a `config.toml` file (if one doesn't already exist). The contents of this file should be as follows
	create a `config.toml` file (if one doesn't already exist). The contents of this file should be as follows:

	This file will probably be at `godot/EXTENSIONNAME.gdextension`.
	This file will probably be at `godot/{YourCrate}.gdextension`.

	The format will be similar to the following
	The format will be similar to the following:

	At the same level as your `Cargo.toml`, create a `.config` directory and inside of that,
	At the same level as your `Cargo.toml`, create a `.cargo` directory and, inside of that,

	The reason that a nightly `rustc` is required is that nightly is required to build `std` (`-Zbuild-std`).
	The reason why nightly `rustc` is required is the unstable flag to build `std` ([`-Zbuild-std`][flag-build-std]).

	Next, install Emscripten. The simplest way to achieve this is to install `emsdk` from the git repo. Recommended to use version 3.1.39 for now[^1]
	Next, install Emscripten. The simplest way to achieve this is to install [`emsdk` from the git repo][emsdk-git].
	We recommend version 3.1.39 for now.[^1]

	It would also be HIGHLY recommended to follow the instructions in the terminal to add `emcc`[^2] to your `PATH`.
	It would also be highly recommended to follow the instructions in the terminal to add `emcc`[^2] to your `PATH`.

	The contents of this file need to contain the following:
	This file needs to contain the following:

		web.debug.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/debug/EXTENSIONNAME.wasm"
		web.release.wasm32 = "res://../rust/target/wasm32-unknown-emscripten/release/EXTENSIONNAME.wasm"

		Add a web export in the Godot Editor. In the top menu bar, go to `Project > Export...` and configure it there.
		Make sure to turn on the `Extensions Support` checkbox.

	"-C", "link-args=-pthread",
	"-C", "link-args=-pthread", # was -sUSE_PTHREADS=1 in earlier versions

Web exports guide #15

Web exports guide #15

Conversation

Esption commented Nov 27, 2023

PgBiel left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bromeon left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bromeon Nov 28, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Esption commented Nov 28, 2023

PgBiel Nov 28, 2023 • edited Loading

Choose a reason for hiding this comment

Bromeon left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

PgBiel Nov 29, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bromeon left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bromeon commented Dec 12, 2023

Bromeon left a comment •

edited

Loading

Bromeon Nov 28, 2023 •

edited

Loading

PgBiel Nov 28, 2023 •

edited

Loading

Bromeon left a comment •

edited

Loading

PgBiel Nov 29, 2023 •

edited

Loading