Qt-contributors-summit-2013-QBS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<span class="caps">QBS</span> | |||
Released version 1.0. | |||
replacing qmake for Qt: | |||
* https://bugreports.qt.io/browse/QBS-70 | |||
* cannot replace configure (yet) | |||
* cannot replace syncqt (yet) | |||
bootstrapping qbs: | |||
* current dependencies: QtCore, QtConcurrent, QtScript | |||
* Ossi volunteered to tackle the bootstrapping issue | |||
* QtScript could maybe replaced by v4m | |||
* Qt bootstrap libs do not support qobjects or qtconcurrent | |||
* Maybe replace bootstrap lib altogether with a static build? | |||
Ideas for language: | |||
* Why isn’t e.g. cpp dependency built in / depends on file suffix? This would allow a product to depend e.g. on variable file list | |||
* Does qbs right now support the generation of an unknown number of files out of one file (and process these further)? No, not yet. This problem is similar to moc support which is currently hard-wired into qbs. | |||
Is qbs any more toolable than qmake, if you allow arbitrary js in properties? | |||
* common use cases are easily toolable | |||
* complicated parts must be edited manually |
Revision as of 14:06, 25 February 2015
QBS
Released version 1.0.
replacing qmake for Qt:
- https://bugreports.qt.io/browse/QBS-70
- cannot replace configure (yet)
- cannot replace syncqt (yet)
bootstrapping qbs:
- current dependencies: QtCore, QtConcurrent, QtScript
- Ossi volunteered to tackle the bootstrapping issue
- QtScript could maybe replaced by v4m
- Qt bootstrap libs do not support qobjects or qtconcurrent
- Maybe replace bootstrap lib altogether with a static build?
Ideas for language:
- Why isn’t e.g. cpp dependency built in / depends on file suffix? This would allow a product to depend e.g. on variable file list
- Does qbs right now support the generation of an unknown number of files out of one file (and process these further)? No, not yet. This problem is similar to moc support which is currently hard-wired into qbs.
Is qbs any more toolable than qmake, if you allow arbitrary js in properties?
- common use cases are easily toolable
- complicated parts must be edited manually