Skip to content

Qmake backend and new language features

Latest
Latest
Compare
Choose a tag to compare
@rochus-keller rochus-keller released this 16 Dec 23:40
· 34 commits to main since this release
2020-12-16
4562a4f

I'm pleased to announce the availability of the BUSY qmake generator. It is called by adding the -G qmake option to the command line. The result is a top-level qmake SUBDIRS project file with a subdirectory/project file per BUSY Product instance in use, compatible with qmake/Qt 5.

Moc and Rcc support is implemented, als well as LuaScript support. The generator provides the required script and configuration files, and for some functions the Lua VM compiled with BUSY is called (to provide for BUSY features not natively supported by qmake). Dependencies are considered, so that the affected source files are recompiled and the binaries are updated to account for the change.

See the current LeanQt version for a representative example and a description on how to use the qmake generator.

New BUSY specification language features

During the development of LeanQt, the need for a few language extensions arose. These extensions were kept as minimal as possible.

  • A submod declaration can now have a path to an alternative BUSY file which is used in case the subdirectory referenced in the declaration is not available. This makes it possible to delete the parts from the source tree that are not needed for a particular configuration without breaking the consistency of the build specification. See here for more information.
  • New modname() predeclared function, see here for more information.
  • New set_defaults() predeclared procedure to set the global configuration to be used for a given toolchain; this configuration is useful to e.g. enable or disable compiler optimizations or debug symbol generation for the whole project at once; see here for more information.
  • The Moc and Rcc classes each have a new tool_dir field of path type which can be used to override the path set in the global moc_path and rcc_path variables; see here for more information.

Breaking changes in the BUSY specification language

  • The predeclared global variables moc_path and rcc_path no longer point to the executable file, but instead to the directory where BUSY looks for the moc or rcc executable.
  • The outputs field of the Copy class is now relative to the path given by the root_build_dir predeclared variable (no longer relative to the subdirectory in the build tree associated with the Copy declaration).

Limitations of the qmake generator

  • LuaScriptForEach is not yet generated for qmake (will be added in future); instead a warning is issued.
  • Message is not generated for qmake; instead messages and errors are issued by the qmake generator itself.
Assets 2
Loading