Release the CheerpJ JNI headers:
#27 (comment):
We could experimentally build LWJGL3 by using some unsound hacks, but these hacks are too unstable to be published. The library uses some JNI features which are not currently supported properly by our JNI implementation for CheerpJ.
Our plan is eventually release our JNI headers and library and allow CheerpJ users to compile their own libraries to WebAssembly, but this is something that we cannot prioritize at this time.
I'll keep this issue open as support for LWJGL3 is something that we want to eventually provide
(posted 2026-05-01T07:43:13Z, see https://api.github.com/repos/leaningtech/browsercraft/issues/comments/4358369393, updated_at tag)
#8 (comment):
Although we have internally achieved up to 1.16.5, there is further work required that we cannot schedule at this time.
Moving a few version further would not truly make a difference in the value of this demo, so that is also not a priority.
(posted 2025-04-10T18:22:53Z, see https://api.github.com/repos/leaningtech/browsercraft/issues/comments/2794764317, updated_at tag)
1.16.5 implies LWJGL3
Releasing the JNI headers would allow many native libraries to be compiled to wasm a natively used with cheerpj without having to port them to javascript.
Release the CheerpJ JNI headers:
#27 (comment):
(posted 2026-05-01T07:43:13Z, see https://api.github.com/repos/leaningtech/browsercraft/issues/comments/4358369393, updated_at tag)
#8 (comment):
(posted 2025-04-10T18:22:53Z, see https://api.github.com/repos/leaningtech/browsercraft/issues/comments/2794764317, updated_at tag)
1.16.5 implies LWJGL3
Releasing the JNI headers would allow many native libraries to be compiled to wasm a natively used with cheerpj without having to port them to javascript.