Skip to content
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

Problem building emscripten cross #113

Open
j-mckim opened this issue Mar 11, 2022 · 0 comments
Open

Problem building emscripten cross #113

j-mckim opened this issue Mar 11, 2022 · 0 comments

Comments

@j-mckim
Copy link

j-mckim commented Mar 11, 2022

Attempting to run cmake to build the webasm environment fails and elicits these two diagnostics:

$ mkdir b3 && cd b3 && emcmake cmake ..
configure: cmake .. -DCMAKE_TOOLCHAIN_FILE=/home/jim/src/emsdk/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake -DCMAKE_CROSSCOMPILING_EMULATOR=/home/jim/src/emsdk/node/14.15.5_64bit/bin/node;--experimental-wasm-threads
-- NanoGUI v0.1.4
-- Setting build type to 'Release' as none was specified.
-- NanoGUI: using GLES 2 backend.
-- NanoGUI: building static library.
CMake Error at CMakeLists.txt:505 (install):
install DIRECTORY given no DESTINATION!

CMake Error at CMakeLists.txt:525 (configure_package_config_file):
Unknown CMake command "configure_package_config_file".

-- Configuring incomplete, errors occurred!
See also "/home/jim/src/nanogui/b3/CMakeFiles/CMakeOutput.log".
emcmake: error: 'cmake .. -DCMAKE_TOOLCHAIN_FILE=/home/jim/src/emsdk/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake -DCMAKE_CROSSCOMPILING_EMULATOR=/home/jim/src/emsdk/node/14.15.5_64bit/bin/node;--experimental-wasm-threads' failed (returned 1)

This is using the current emscripten, via a git clone.

Per some advice I read while researching the diagnostics, I patched CMakeLists.txt to 'include(CMakePackageConfigHelpers)' patch.txt
. That eliminated the "unknown command" diagnostic.

With respect to the "install DIRECTORY given no DESTINATION!" diagnostic, I'm working around that by making NANOGUI_INSTALL default to 0. I know this isn't the correct fix, but I don't have a good understanding of what is the correct action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant