The qiproject.xml file should always be at the top of a project registered in a worktree
It can optionally contains paths to subfolders, so that you can have nested projects.
<project version="3" />
<project src="subfolder" />
</project>
This is the basis for every qiBuild tool.
Each tool then parses the same file using its associated tags, ignoring the rest.
This helps having loosing coupled dependencies between the various tools.
There can only be one qibuild project per source.
The CMakeLists.txt must be next to the qiproject.xml
The qiproject.xml must contain a qibuild element.
The qibuild element must contain a name attribute.
The name of the project must be unique in the worktree.
The list of dependencies is given as a white space separated name list in a names attribute (note the plural form).
The names can be other projects in the same work tree, or the name of packages in a toolchain.
The dependencies can be of two sorts:
You can mix them using the buildtime="true" and runtime="true" attributes:
For instance
<project version="3" >
<qibuild name="hello">
<depends buildtime="true" runtime="true" names="foo bar" />
<depends runtime="true" names="spam" />
</qibuild>
</project>
Here runtime dependencies are foo, bar and spam, and buildtime dependencies are just foo and bar.
This is the configuration for adding translations to your source code. This configuration is used by qilinguist to generate translation files and install rules.
The file will look like:
<project version="3" >
<translate domain="hello" linguas="fr_FR en_US" tr="gettext" />
</project>
Tags definitions: