Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
QtCS2017 QtQuickControlsDeployment
(Redirected from Deployment Challenges with QtQuick.Controls(2) applications)
Jump to navigation
Jump to search
Meeting minutes from (Qt Quick Controls) Deployment Challenges, QtCon 2017
Organizer: Nils Jeisecke Notetaker: Kai Koehne
- First user experience is bad
- windeployqt does expect qml files in subdirectory
- Qt Creator template puts main.qml in top level file
- Files / resources mess
- Documentation for QQ Controls 1: "Everything is in resources"
- windeployqt copies a lot of .qml files though
- Also .qmlc files are copied by windeployqt
- Comment: All these .qml files are prob a bug in Qt Quick Controls 1 build scripts
- Comment: We probably copy them for debugging/profiling
- Difference between static and dynamic builds
- Static builds: .qml files for imports are put into the executable
- Dynamic builds: single .qml files are shipped
- This is not reflected by documentation though
- Why is Qt resource system better
- Unified approach on all platforms
- Code signing
- .qmlc
- Same problems are there for Qt Quick Controls 2: QTBUG-48386
- Why is 'qmltooling' deployed by windeployqt?
- Useful for debugging and profiling
- There's no clear distinction though between 'deployment' to a device, and generating a final package.
- Conclusion
- We think Qt resource system should be the way to go
- Anhow, we miss the right people in the session to decide this. Let's try to schedule a second slot.
- (Update: Since it relates closely to Qt Quick, the suggestion is to bring this up in the 'New QML compiler infrastructure' session)
- (Update: lots of ideas: QtCS2017 Qt Deployment Story)