Build all plugins against current Psi API - #149
Merged
Merged
Conversation
Ri0n
marked this pull request as ready for review
August 30, 2026 23:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a real full-plugin CI build instead of relying only on qca-otr smoke tests.
The workflow shallow-clones current psi-im/psi and uses its plugin SDK headers/CMake variables via PLUGINS_ROOT_DIR. It builds all generic and dev plugins on every pull request and every push to master for both Qt 5 and Qt 6.
The normal full build intentionally does not install libotr/libgcrypt/libgpg-error, so legacy runtime dependency regressions fail visibly. QCA 3.0.5 is provided using the released Ubuntu Qt6 packages and a minimal Qt5 source build.