Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
Qt Creator 4.12.0-beta1
-
None
-
-
0d9b0f8074b4328cf5ec1141904aeff6a0a2f9f9 (qt-creator/qt-creator/master)
Description
The WebAssembly plugin auto-detects a compiler with a distinctive ABI. If Qt Creator is launched once with the plugin disabled, the Kit is invalid, because neither compiler nor device are set. That's expected, and we live with that since the WebAssembly Plugin is experimental.
But if Qt Creator is then restarted with the plugin enabled, the kit remains invalid due to non-set compiler. That is a regression in 4.12-beta1, it used to work in 4.11. In 4.11, the Kit would be auto-repaired, because the right compiler gets auto-magically set.
If I start Qt Creator with the WebAssembly plugin on, the first time after installing the Qt versions via SDK, everything still works fine.
Attachments
Issue Links
- relates to
-
QTCREATORBUG-23360 Registration of WebAssembly Kit (with valid device) fails
- Closed
- resulted from
-
QTCREATORBUG-23561 WebAssembly kit not detected
- Closed
For Gerrit Dashboard: QTCREATORBUG-23564 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
289928,3 | QtSupport: Try harder to ensure that Qt kits have a toolchain | master | qt-creator/qt-creator | Status: MERGED | +2 | 0 |