Fix using qibuild make-host-tools when no project is specified
Implement qibuild make-host-tools --all
qibuild configure: fix setting flags containing =, such as qibuild configure -DCMAKE_CXX_FLAGS="-std=gnu++11"
qibuild configure: set QI_VIRTUALENV_PATH to the virtualenv path that has been created by qipy bootstrap. This is useful if you want to call Python code from C++.
Fix using qibuild clean in some corner cases
Restore build directory paths when using a build prefix.
Support setting arbitrary environment variables in ~/.config/qi/qibuild.xml. Here’s an example of a build configuration using clang
<qibuild>
<config name="clang">
<env>
<var name="CC">clang</var>
<var name="CXX">clang++</var>
</env>
</config>
</qibuild>
qibuild package: add --standalone option. This generates a package containing the runtime components and all the runtime dependencies. Useful to redistribute compiled binaries.
qibuild package: add --breakpad option. This generates a symbols archive to be used with breakpad.
Using qibuild set-host-config twice with different configuration names lead to undefined behavior.
Fix using qibuild run in some corner cases.
Always generate a share/qi/path.conf during installation. (This is required by libqi)
When reading ~/.config/qi/qibuild.xml, prepend contents of <env path="..."/> after launching bat file.
Using qibuild set-host-config twice with different configuration names lead to undefined behavior.
qibuild config --wizard: fix infinite loop when asking for QtCreator application path
qipkg deploy-package: now also accept a .pml path as argument.
This means you can do
qipkg deploy-package foo.pml --url user@host
Instead of:
qipkg make-package foo.pml
qipkg deploy-package foo-0.1.pkg --url user@host