| Age | Commit message (Collapse) | Author |
|---|
|
GCC 10 ICE's[1] in qt_connection_util.h code; and ubuntu-20.04 doesn't
have GCC 11.
Also: patch a Qt 5.15 header when compiling with GCC because a
combination of Qt 5.15 and GCC 11 in turn triggers QTBUG-91909/90568...
Which in turn required moving Qt setup before the build environment
setup. Life's fun.
[1] Internal Compiler Error
|
|
|
|
|
|
Also: build with Qt 6 first, so that it fails sooner.
|
|
- CodeQL analysis was executed on every job that ran Clang, humping
the total execution time by 10+ minutes alone. Now it only runs on
a single job.
- libolm is no more compiled but installed from the repo, along with
libssl-dev; and both are installed in the same transaction as ninja
and valgrind, shaving out one apt transaction
- One more Windows job has been added to test building with Qt 6.3.1
on that OS.
- Qt version is pushed earlier in the job matrix, as it becomes more
significant than the compiler for a given platform.
|
|
Qt 6 builds are allowed to fail for now.
|
|
Also, use MSVC 2019 on Windows.
|
|
|
|
It takes well over an hour to build the whole lineup for now; while
the single right fix for that is making quotest capable of running in
parallel, a few GCC jobs can be safely dropped for now (and we'll see
if they should be brought back when parallel quotest unleashes the CI).
|
|
|
|
Also: make all cloning for update-api shallow, for optimisation.
|
|
|
|
Also: use quotient-im/matrix-spec main branch again, now that it has
adjusted definitions; drop un(der)used partials
|
|
QtKeychain master suffers from
https://github.com/frankosterfeld/qtkeychain/issues/213.
|
|
|
|
|
|
Building with static libs fails on QtKeychain apparently underlinking
with glib when --coverage is passed.
|
|
|
|
|
|
On other platforms Docker fails to stand up the container.
|
|
To use this in CI required extending/fixing autotests/run-tests.sh:
it can now accept arguments that are further passed to ctest invocation,
and it no more cd's to the build directory because build directories
can be in all kinds of places, expecting the caller to pick
the directory upfront.
|
|
The whole cycle will get terribly long again; looking forward to
parallel quotest...
|
|
The result is FTBFS as yet; next commits will fix that, along with a few
other things.
|
|
|
|
On Windows and macOS, the assumed practice is to package things up in
a monolithic distribution package. On Linux, fine-grained library
packages are installed.
After adding CMAKE_INSTALL_RPATH_USE_LINK_PATH dynamic linkage is
testable on macOS but that's not the "proper" way to install things on
the platform, anyway. It also probably works on Windows but I couldn't
get a workable setup for quotest after a few attempts. Perhaps it's
a matter of running windeployqt instead of trying to figure out and
add to PATH all the locations needed; or maybe not; I don't have the
motivation to explore this further.
|
|
|
|
|
|
|
|
For now on Linux with GCC only, with a plan to add Windows eventually.
|
|
|
|
It's been alright with the comment inside the script.
|
|
Comments inside shell scripts apparently break the flimsy GHA machinery.
|
|
|
|
|
|
That apparently confuses Sonar as it fails to match the source files.
|
|
|
|
...instead of hoping the thing will sort itself out because CLion does.
|
|
For coverage analysis to work, a test run is needed, making the overlap
between ci.yaml and sonar.yml quite significant again.
Note: 'update-api' option is temporarily dropped from the matrix
to speed up the check. If things run fine, 'update-api' will come back.
|
|
|
|
There's not much value in analysing the code without E2EE and with E2EE
because E2EE is additive; and there's no plan to look close into
the generated API code apart from what already ends up being committed.
|
|
CMAKE_INSTALL_RPATH_USE_LINK_PATH is more universal than setting LD_LIBRARY_PATH
Also: drop an extra slash in the path to installed quotest.
|
|
|
|
This covers Quotient_INSTALL_TESTS setting.
|
|
|
|
It turned out that, confusingly, ${{ runner.workspace }} refers to
the directory above $GITHUB_WORKSPACE, which is why the previous commit
ended up with valgrind not finding its suppressions.
|
|
|
|
|
|
|
|
|
|
|
