Qt 6.0.0 Known Issues: Difference between revisions
No edit summary |
|||
| Line 2: | Line 2: | ||
*Check that your system meets [https://doc-snapshots.qt.io/qt6-dev/gettingstarted.html#platform-requirements%20Qt's%20requirements] | *Check that your system meets [https://doc-snapshots.qt.io/qt6-dev/gettingstarted.html#platform-requirements%20Qt's%20requirements] | ||
*All open issues can be found from Jira: https://bugreports.qt.io | *All open issues can be found from Jira: https://bugreports.qt.io | ||
**RTA findings [https://bugreports.qt.io/issues/?filter= | **RTA findings [https://bugreports.qt.io/issues/?filter=22662 here] | ||
== All platforms == | == All platforms == | ||
Revision as of 15:15, 6 October 2020
- Check that your system meets [1]
- All open issues can be found from Jira: https://bugreports.qt.io
- RTA findings here
All platforms
Windows
Linux
macOS
Android
- QMake script has a hardcoded path to the host qmake from the built environment in CI. A workaround is to manually edit android_<abi>/bin/qmake to use the host's qmake path. See QTBUG-87071.
- If you don't have a system-wide cmake installed, or if cmake is not in the PATH, add it to the PATH, otherwise, qt-cmake will not find a usable cmake. See QTBUG-87071.
- On Windows hosts, building, and packaging an APK has issues with path formats. See QTBUG-87066 for manually applying the fixes. These fixes will be included in the next beta release.
- qt-cmake has hardcoded value for the Android toolchain file from CI, that's why additional args must be provided to qt-cmake, use the following command (see QTBUG-87068):
<qt_android_install>/bin/qt-cmake -S <source_path> -B <build_path> -DANDROID_SDK_ROOT:PATH=<sdk_path> -DANDROID_ABI:STRING=<abi> -DANDROID_NATIVE_API_LEVEL:STRING=23 -DCMAKE_TOOLCHAIN_FILE:PATH=<ndk_path/build/cmake/android.toolchain.cmake -DCMAKE_FIND_ROOT_PATH:PATH=<qt_android_install> -DQT_HOST_PATH:PATH=<qt_host_install>
iOS
- Using CMake to build user projects requires manual tweak. Please use qmake for now.