v3.2¶
Command line¶
- New command added:
qitest. This makes it possible to run the tests after they have been deployed to a remote host (assuming qibuild is installed on the remote host)
qibuild deploy --with-tests user@host:deploy
ssh use@host
cd deploy
qitest run qitest.json
qibuild¶
API break:
--cmake-generator,-Goption can now only be used forqibuild configure.For the other build actions (
qibuild make,qibuild install, ...), the CMake generator is now simply read from the CMake cache in the build directory.New configure options:
--32bits: force 32bits build even on 64bits platform (linux only)--with-debug-info: force inclusion of debug symbols when building with--release(useful when using breakpad)--without-debug-info: force exclusion of debug symbols when building with--debug(useful when making redistributable debug libraries for Visual Studio)
Faster
qibuild deploy: now using a single rsync call using a file list.Show what is currently building in the title bar (linux only)
Better error message when CMake segfaults
Sort projects and packages lists in qibuild deploy
qibuild test:- Now the same as
qitest run <build>/qitest.json ctrl-ccan no longer cause deadlocks.- Displays a summary even when it has been interrupted
- Python exceptions raised during tests no longer cause deadlocks.
- Tests are now run from
<build>/sdk/binby default.
- Now the same as
On Mac,
.afiles from packages are no longer installed when using--runtime
qitoolchain¶
- Fix
qitoolchain set-defaulterasing profile settings
qidoc¶
- Output where the doc has been built
qisrc¶
- Faster
qisrc sync: only configures the projects we want to sync, instead of all the projects in the worktree qisrc foreach: add-g,--groupargumentqisrc grep: forward color options togitgit.is_git: optimize detection: does .git exist?qisrc sync: do not crash when fetch failsqisrc snapshot: handle badly formatted snapshot file
Python¶
- Rewrite of the
qibuild testimplementation- Removed
qibuild.ctestandqibuild.performance - Added
qitestmodule,qibuild.test_runnerandBuildProject.run_tests
- Removed
CMake¶
- Added
qi_create_test_helper: this will create an executable that will be built when the tests are built, but is not an actual tests. Useful to create several tests with the same executable but different arguments:
# old:
qi_create_test(foo foo.cpp NO_ADD_TEST)
qi_add_test(foo_bar foo ARGUMENTS --bar)
qi_add_test(foo_baz foo ARGUMENTS --baz)
# new:
qi_create_test_helper(foo foo.cpp)
qi_add_test(foo_bar foo ARGUMENTS --bar)
qi_add_test(foo_baz foo ARGUMENTS --baz)
Changed options:
BUILD_TESTSis no longer used, useQI_WITH_TESTS=OFFinstead to deactivate the tests completely (they won’t even be configured)The implementation no longer calls upstream’s
add_test, which means:- You cannot use
ctestormake testto run the tests - The call to
enable_testing()is no longer necessary
- You cannot use
qi_add_testaddNO_INSTALL,WORKING_DIRECTORYandENVIRONMENToptionsqi_swig_java: addOUTDIRparameter, used to specify where swig will generate data.qibuild cmake modules:
boostutils: fix for cmake > 2.8.11
Packaging¶
- Switch to
setuptools.- Fix using
qidocafter usingpipto installqibuild - Fix using
pip install qibuildon Windows
- Fix using