You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using draco in out cpp side and our web side and have recently started to use webassembly with emscripten to to build our cpp so we can use it in the browser.
For this we need to link to the draco libraries but the default emscripten build does not produce the libdraco, libdracodec and libdracoenc libraries. We currently edit the CMakeList.txt entry at line 607 from:
#
# Draco targets.
#
if (EMSCRIPTEN)
to
#
# Draco targets.
#
if (NO)
So that the emscripten build produces the libraries the same way the cpp build does.
What would be really useful for us would be a CMake flag that if it were set and emscripten was being used we could build only the three library files.
Cheers
The text was updated successfully, but these errors were encountered:
Downstream users sometimes need the standard Draco library targets,
even when building in Emscripten. Add the flag ENABLE_JS_GLUE, which
defaults to ON. When turned OFF, the standard Draco library targets
will still be built within an Emscripten build.
Also do some whitespace clean up while working in CMakeLists.txt.
#407
Downstream users sometimes need the standard Draco library targets,
even when building in Emscripten. Add the flag ENABLE_JS_GLUE, which
defaults to ON. When turned OFF, the standard Draco library targets
will still be built within an Emscripten build.
Also do some whitespace clean up while working in CMakeLists.txt.
google#407
We are using draco in out cpp side and our web side and have recently started to use webassembly with emscripten to to build our cpp so we can use it in the browser.
For this we need to link to the draco libraries but the default emscripten build does not produce the libdraco, libdracodec and libdracoenc libraries. We currently edit the CMakeList.txt entry at line 607 from:
to
So that the emscripten build produces the libraries the same way the cpp build does.
What would be really useful for us would be a CMake flag that if it were set and emscripten was being used we could build only the three library files.
Cheers
The text was updated successfully, but these errors were encountered: