-
Notifications
You must be signed in to change notification settings - Fork 231
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
"official" support for building msc_basis_transcoder as asm.js instead of wasm? #332
Comments
Ah. Looks like the Draco documentation may be a little bit outdated, but their cmake checks for an |
Poor souls that have to support IE11 or other legacy browsers (via asm.js) can test the web_legacy_asm_js branch :) I tested it successfully with Emscripten 1.38.48 fastcomp. Not tested with Emscripten upstream yet. @likangning93 If this works for you I can create a PR |
Make sure you follow the asm.js build instructions |
@likangning93 is this still an issue for you? If so, did you test @atteneder 's branch? |
Ping @likangning93. If I don't here from you in a couple of days I'm going to close this as not planned. |
…or Emscripten (fixes KhronosGroup#332)
Draco includes documentation for building their encoder/decoder to asm.js as a fallback for use cases where
WebAssembly
isn't available, for example, if a user is required to use Internet Explorer 11: https://github.com/google/draco/blob/master/BUILDING.md#javascript-encoderdecoderCan this project add official support too? I was able to build a working (in my testing) transcoder by modifying the cmake variable
KTX_EMC_LINK_FLAGS
to include flagsWASM=0 LEGACY_VM_SUPPORT=1 --memory-init-file 0
:However, this prevents the rest of the build from completing, since it seems there's testing code that still expects the
wasm
files to exist:Ideally for our use case we also wouldn't want to have to monkeypatch
KTX-Software
every time we update our copy of the transcoder.The text was updated successfully, but these errors were encountered: