In order to implement Qt Android multi-ABI packages for https://bugreports.qt.io/browse/QTBUG-80943
one idea was to allow creation of Coin configurations that can depend on other multiple target configurations to run some special instructions. This is somewhat of a second layer extension to the existing platform dependency concept.
Have 1 host platform config: Windows-MinGW -> builds Qt for MinGW
Have 4 target Android platform configurations depending on the Windows host: arm64, arm7, x86, x64 -> builds for Qt for Androids
Have 1 Android stitching super-job: Depends on the previous 4 target Android configs.
Retrieves all artifacts from the above 4 configs for each repo, runs some build system script to stitch the 4 artifacts for each repo, create 1 stitched output artifact for each repo.
These artifacts would then be considered Packaging artifacts, to be used by the Qt package creation pipeline.
Would this be feasible to implement?