Unify build configs: now a build config has a name, a toolchain and a list of profiles. A build dir matches exactly one build config. Build directories are the same when building in release or in debug.
To do the transition, you should create at least one config per toolchain, for instance:
qibuild add-config nao --toolchain atom --profile nao
Then use
qibuild configure -c nao
As a consequence, the -p, --profile option is gone, and --release can only be used for qibuild configure
Add qibuild add-config, qibuild list-configs, qibuild rm-config
qibuild clean: fix when using remote profiles
qibuild init: honor -w, --worktree option
Re-implement setting a custom build prefix. (The feature was gone since qibuild 3.0)
To use this feature, write something like:
<qibuild>
<build prefix="my-build" />
</qibuild>
in /path/to/worktree/.qi/qibuild.xml
You can also use --build-prefix in your calls to qibuild configure, qibuild make and so on.
Note that the old syntax, using <build build_dir="my-build> is no longer supported.
Also note that the build directories that will be created will be like <prefix>/<project>/<build-dir> instead of <prefix>/<build-dir>/project
Changes in handling dependencies to packages in the toolchain:
CMAKE_PREFIX_PATH is set in the dependencies.cmake file, no longer in the generated toolchain file
Optionally use qiproject.xml information instead of adding every path of every package in CMAKE_PREFIX_PATH
(This behavior is triggered by setting the QIBUILD_STRICT_DEPS_RESOLUTION environment variable for now, but will be the default in the next release)
qibuild find: fix return code when no CMake module is found
Fix using -j with Visual Studio generators.
Include toolchain paths in path.conf
qibuild: generate qitest.json file also after building
Store default config for worktree in the global config file (~/.config/qi/qibuild.xml)
qibuild deploy: make specifying user and port optional (this allows to specify them in ~/.ssh/config)
Put staged directories with qi_stage_dir first in path.conf