P3: Somewhat important
For platforms like Android and WebAssembly a separate toolchain file needs to be chainloaded from either the Android NDK or emscripten SDK.
When using a Qt online installed Qt's qt-cmake on the command line to configure a a project, configuration fails because the chainloaded toolchain file path from the CI is not present on the local machine.
The user is then forced to explicitly pass a -DQT_CHAINLOAD_TOOLCHAIN_FILE to their local SDK toolchain path. The Android qt.toolchain.cmake at least mentions the option, the WebAssembly one doesn't.
We should investigate if it's feasible to detect the NDK or emsdk env vars and derive the toolchain file paths from them.
I'm guessing when using Qt Creator, it's not a problem because Creator sets the relevant options.
|For Gerrit Dashboard: QTBUG-96843|
|373101,5||CMake: Split and clean up WebAssembly auto-detection code||dev||qt/qtbase||Status: MERGED||+2||0|
|373102,8||CMake: Get toolchain file path from EMSDK env for Wasm user projects||dev||qt/qtbase||Status: MERGED||+2||0|
|373324,4||CMake: Show error in user projects if wasm toolchain file not found||dev||qt/qtbase||Status: MERGED||+2||0|
|373447,2||CMake: Split and clean up WebAssembly auto-detection code||6.2||qt/qtbase||Status: MERGED||+2||0|
|373448,3||CMake: Show error in user projects if wasm toolchain file not found||6.2||qt/qtbase||Status: MERGED||+2||0|
|373449,2||CMake: Get toolchain file path from EMSDK env for Wasm user projects||6.2||qt/qtbase||Status: MERGED||+2||0|