QtCS2017 BOF Build Systems

• Meson
  • Did anyone use it?
  • Tobias: Tried it out, "kind of works"

• Build System of Qt
  • Keeping QMake alive
  • Converting #ifdef'ed to new module system
  • Test for configure can now be done in the .json file
  • Configure system will also be used in qbs

• Qbs
  • Is it still using QtScript?
    • Still using QtScript as backend
    • Bootstrapping will use it, too
  • Moving Qbs itself away from Qt -> stl
  • Shall we use full JavaScriptCore?
    • Lars: Rather use v4 directly, let's not have two engines
  • Looked at Ducktape as alternative, but was buggy
  • Thiago volunteered to help communicating
    • Jerry-Script is an another alternative
  • What about Linux distributions?
    • We don't have to support old compiler versions
    • Don't we? People still use older versions
    • Can we requirement VS 2017 for Qbs?
      • probably not any time soon
      • we at minimum have to keep QtC's compilers working
  • How to distribute?
    • Ossi: Two different sources, one boot-strappable, another one just qbs

• Can we make moc and rcc independent from Qt?
  • Why is this needed?
  • With qmake gone in the future, there's only moc/rcc to be bootstrapped
    • Can we use the tools that are on the host for cross-compilation?
    • Cross-compilation should allow using host tools from other Qt

• QBS/qtbase prototype
  • Ongoing work to clean up issues with the first prototype last year

• Making Qt installation relocatable?
  • More robust path handling?
  • Policy questions related to deployment
  • Let's do another session on this