Unity uses the Emscripten compiler toolchain to cross-compile the Unity runtime code written in C and C++ into WebAssembly (also called Wasm). Emscripten generates small code, is load-time and memory efficient, and aims to deliver close to native speed execution. For more information about Wasm in Unity, refer to the WebAssembly is here blog post.
Unity uses IL2CPP to convert the .NET game code in your C# scripts to Wasm. IL2CPP takes .NET bytecode and converts it to corresponding C++ source files, which is then compiled using Emscripten to convert your scripts to Wasm.
Unity bundles the Emscripten compiler with the WebGL platform package, so that you don’t have to manually download it. The version of Emscripten that the Editor uses varies by Editor version:
Unity 版本 | Emscripten version | Supported native plug-in file formats |
---|---|---|
Unity 2022.2 and later | Emscripten 3.1.8-unity | .a, .bc |
Unity 2021.2 and later | Emscripten 2.0.19.6-unity | .a, .bc |
Unity 2019.2 to 2021.1 | 1.38.11-unity | .bc |
Unity 2018.4 up until Unity 2019.2 | 1.37.40-unity | .bc |
Unity 2018.2 up until Unity 2018.4 | 1.37.33-unity | .bc |
注意:
The following list provides expansion for the acronyms of file formats listed in the above table:
.a
).o
).bc
)With Emscripten versions before Emscripten 2.0, Unity recommends building Bitcode
plug-ins (files of type .bc
). From Emscripten 2.0 onwards, Unity recommends to build Wasm Object File
plug-ins that are Wasm object files of type .o
, bundled into GNU archive files of type .a
.
You can determine the path to the exact version of Emscripten toolchain from the emscripten-version.txt
located at:
C:\Program Files\Unity\Hub\Editor\<Editor version>\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten\emscripten\emscripten-version.txt
If you’re creating native C/C++ plug-ins for your Unity application, you can either bundle the C/C++ code with your project (see Native plug-ins) or build the native code to a plug-in archive ahead of time with the Emscripten compiler toolchain.
If you choose to build plug-in code in advance, you should use the Emscripten compiler toolchain. To ensure LLVM binary format compatibility, the version of Emscripten that’s used to compile the plug-ins must match the version of Emscripten that Unity uses.
Typically, plug-ins are compiled to a static library archive format. For versions before Unity 2021.2 (Emscripten 2.0), LLVM Bitcode file format (.bc
) is the preferred plug-in format.
From Unity 2021.2, the preferred plug-in format is GNU archive file format (.a
) that contain WebAssembly Object Files (.o
). Although, earlier LLVM Bitcode .bc plug-in files are still supported, using them might have a negative impact to compilation times.
Note: When migrating a native plugin from one Unity version to a version that uses a different version of Emscripten, Unity recommends to recompile the Unity plug-in from source, because the LLVM compiler project doesn’t guarantee binary compatibility of build artifact files across compiler versions.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.