13bf20c8aa
Emscripten's option for enabling asyncify (-sASYNCIFY) is a link-time option, which means there is no requirement to have a separate asyncify build, at least for static builds. Replace the current QT_HAVE_EMSCRIPTEN_ASYNCIFY compile-time option with a run-time option which checks if the asyncify API is available. Keep support for configuring with "-device-option QT_EMSCRIPTEN_ASYNCIFY=1" for backwards compatibility and for the use case where want asyncify support to be on by default for a given Qt build. Enable asyncify for the asyncify_exec example. Change-Id: I301fd7e2d3c0367532c886f4e34b23e1093646ad Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> (cherry picked from commit f347682fd52fd8e94f15a06cda9f1a64ebc4d552) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Event loop exec() and main() on Qt for WebAssembly
These examples demonstrate how QEventLoop::exec() works on Qt for WebAssembly, and also shows how to implement main() without calling QApplication::exec().
Contents
main_exec Standard Qt main(), where QApplication::exec() does not return
main_noexec Qt main() without QApplication::exec()
dialog_exec Shows how QDialog::exec() also does not return
thread_exec Shows how to use QThread::exec()