Home · Overviews · Reference · Classes codeless banner

QBuild Concepts


When you execute QBuild, you are building a solution. A solution is configured by the file qbuild.solution and if no solution file can be found in the current directory, QBuild will search through the parent directories until it finds one or the root directory is reached. If no solution file is found a default solution is used.

The primary use of the solution is to map physical locations into QBuild's solution filesystem. The default solution maps the root directory.

See qbuild.solution for information about solution files.


A project is defined by the file qbuild.pro.

See qbuild.pro for information about project files.


See extension.js for information about extension files.

Startup Scripts

See qbuild.startup.args and qbuild.startup.js for information about startup files.


QBuild manages 2 types of dependencies. Immediate dependencies and module dependencies. Module dependencies are the preferred kind because they can be loaded in the absense of a source tree. A .dep file is created for every module and depending on that module is a simple as including the file. See module.dep for information about .dep files.

Immediate dependencies are resolved by searching through the available projects and immediately extracting the dependency information. They are primarily used to enable parallel building of projects that depend on each other.

See also Overviews.

Copyright © 2009 Nokia
Qt Extended - QBuild Maintainer Guide