Unvanquished - Recent changes [en-gb]

Compiling the source

Killing time — Sun, 05 Jul 2026 09:49:29 GMT

‎Dependencies: remove Debian packaging scripts discussion

Native Client

Illwieckz — Mon, 22 Jun 2026 03:02:05 GMT

WebAssembly

Illwieckz — Mon, 22 Jun 2026 02:59:17 GMT

Template:NativeClientIsDying

Illwieckz — Mon, 22 Jun 2026 02:58:37 GMT

init

New page

{{note|Thanks to the [[Native Client#Rebuild effort|Rebuild effort]] for both the NaCl loader and the Saigo NaCl compiler, and the fact the Saigo compiler has been maintained by Google up to 2025, bringing Clang 21 and C++23, the NaCl technology may be relevant for another decade and this allows the Unvanquished team to focus resources on other things.

But [[Native Client]] will die one day, and we are slowly preparing the future, and [[WebAssembly]] is the best candidate for a Native Client successor.

It's possible that the actual NaCl death will not come from Google but from Apple when they will deprecate the Rosetta 2 translation layer. If that prevents to run the amd64 loader on Apple Silicon, then Native Client will be dead for macOS and would not be a viable multi-platform sandboxing solution anymore.}}

WebAssembly

Illwieckz — Mon, 22 Jun 2026 02:50:17 GMT

Created page with "'''WebAssembly''' or '''Wasm''' is the best candidate for a future technology used for securely virtualising the game code in the {{engine}}. It may replace Native Client..."

New page

'''WebAssembly''' or '''Wasm''' is the best candidate for a future technology used for securely virtualising the game code in the {{engine}}.

It may replace [[Native Client]] in the engine in the future.

Some work has been started some years ago but for now that effort is stalled.

Thanks to the rebuild effort for both the NaCl loader and the Saigo NaCl compiler, and the fact the Saigo compiler has been maintained by Google up to 2025, bringing Clang 21 and C++23, the NaCl technology may be relevant for another decade and this allows the Unvanquished team to focus resources on other things.

But Native Client will die one day, and we are slowly preparing the future, and WebAssembly is the best candidate for such future.

Native Client

Illwieckz — Mon, 22 Jun 2026 02:46:45 GMT

wording

← Older revision		Revision as of 09:49, 5 July 2026
(3 intermediate revisions by the same user not shown)
Line 215:		Line 215:

	Developpment package name may differs, for example <code>libgmp-dev</code> may be named <code>libgmp3-dev</code> and <code>libglew-dev</code> may be named <code>libglew1.7-dev</code>.		Developpment package name may differs, for example <code>libgmp-dev</code> may be named <code>libgmp3-dev</code> and <code>libglew-dev</code> may be named <code>libglew1.7-dev</code>.
−
−	~~We have a <code>debian</code> directory in the source tree, you can check what's missing this way.~~
−
−	~~cd <var>path/to/unvanquished</var>~~
−	~~dpkg-checkbuilddeps~~
−
−	~~Then install the listed packages this way:~~
−
−	~~sudo apt-get install <var>package list</var>~~
−
−	~~The <code>dpkg-checkbuilddeps</code> command produces no output if you already have the required dependencies.~~
−
−	~~Note that you only need <code>debhelper</code> to build <code>.deb</code> files.~~

	====Fedora====		====Fedora====

@@ Line 2: / Line 2: @@
 It replaced the Q3VM (Quake3 Virtual Machine) in the engine.
 Unlike Q3VM for which the {{code|.qvm}} binaries were limited to be produced with the old C supported by the proprietary LCC compiler, the {{code|.nexe}} NaCl binaries can be compiled with Clang-based open source compilers supporting modern-enough C++ versions and allowing to reuse off-the-shelf C++ libraries that may even be shared between the engine and the game source code.
@@ Line 8: / Line 10: @@
 The Native Client documentation can be found on [https://chrome.jscn.org/docs/native-client/welcome-to-native-client/ chrome.jscn.org/docs/native-client/welcome-to-native-client/].
 ==Platforms==
@@ Line 81: / Line 85: @@
 * https://github.com/Unvanquished/Unvanquished/issues/3197
-== Rebuilding effort ==
+==Rebuild effort==
 The Unvanquished team is working on rebuilding the Native Client ecosystem to benefit from the updates implemented by Google over the years. Especially, this will enable newer C and C++ versions, thanks to the Saigo compiler being based on Clang 21.
@@ Line 97: / Line 101: @@
 It's already possible to build Unvanquished with a Saigo compiler rebuilt this way.
-== Interactive Debugging ==
+==Interactive Debugging==
 Most of the time it is easiest to debug with a native DLL. But if you have a problem that cannot be reproduced outside of NaCl, you may be forced to resort to the following tutorial.
@@ Line 113: / Line 117: @@
 # Start the program by continuing (<code>c</code>).
-== Postmortem Debugging ==
+==Postmortem Debugging==
 See [[Breakpad]].

@@ Line 1: / Line 1: @@
-'''Native Client''' or '''NaCl''' is the current technology used for securely virtualizing the game code in the {{engine}}.
+'''Native Client''' or '''NaCl''' is the current technology used for securely virtualising the game code in the {{engine}}.
 It replaced the Q3VM (Quake3 Virtual Machine) in the engine.
@@ Line 20: / Line 20: @@
 | ✅️ native || ✅️ native || ☑️ through armhf<br/>compatibility || ✅️ native || ✅️ native || ✅️ native || ✅️ native || ☑️ through amd64<br/>compatibility || ☑️ through Linux<br/>compatibility
 |}
 The NaCl loader (the virtual machine running the virtualised code) is available for three systems: Linux, Windows and macOS. The supported architectures differs per system:
@@ Line 79: / Line 81: @@
 * https://github.com/Unvanquished/Unvanquished/issues/3197
-The workspace for our attempt to rebuild and repackage Saigo is there:
+== Rebuilding effort ==
-* https://github.com/DaemonEngine/DaemonSaigoNativeClientToolkit
+It's already possible to build Unvanquished with a Saigo compiler rebuilt this way.
 == Interactive Debugging ==

@@ Line 5: / Line 5: @@
 Some work has been started some years ago but for now that effort is stalled.
-Thanks to the rebuild effort for both the NaCl loader and the Saigo NaCl compiler, and the fact the Saigo compiler has been maintained by Google up to 2025, bringing Clang 21 and C++23, the NaCl technology may be relevant for another decade and this allows the Unvanquished team to focus resources on other things.
+{{NativeClientIsDying}}
-−
-But Native Client will die one day, and we are slowly preparing the future, and WebAssembly is the best candidate for such future.