Details
-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
Description
The goal of this is to better split monolith functions like `qt6_add_qml_module` into separate components like `qt6_target_qml_sources`, `qt6_add_resources`. The idea is to delay and gather all relevant function calls, allowing for more arbitrary ordering of executions
Example
Consider this small example
qt_add_qml_module(foo URI Foo ) qt_target_qml_sources(foo QML_FILES bar.qml ) set_source_files_properties(main.qml PROPERTIES QT_RESOURCE_ALIAS Main )
This one has unexpected failure behavior the `QT_RESOURCE_ALIAS` after it was used in `qt_target_qml_sources`. Keeping track of any such interactions would be tricky for the user, so it would be ideal to remove such interactions
Implications
- More flexibility in the allowed order of function calls
- Less need of forwarding arguments
- Lower configure time because multiple calls like `qt_add_resources` are concatenated
Functions that could be migrated
- `qt6_target_qml_sources`
- `qt6_add_resources`
- ...?
Attachments
Issue Links
- relates to
-
QTBUG-128323 Improve QML iteration speed for shorter build times
-
- In Progress
-
-
QTBUG-116597 qt_internal_add_qml_module should warn about files being added twice
-
- Reported
-