Why is CI building a flutter project seperately for each ABI, why not use the –split-per-abi flag instead of running 3 concurrent builds? I think it would be significantly faster, but maybe there are some concrete reasons why this is not done this way - would like to learn ![]()
we need a separate build block for each arch package
I guess this can be improved, feel free to contribute, but state your ideas first ![]()
To add some background:
- each build block is expected to produce exactly 1 APK
- for Reproducible Builds, APKs need to be matched (the one built here, against the one built by upstream) – so again, a 1:1 relation
As @Licaon_Kter wrote, it’s technically possible to improve that – but that would mean changing a lot of logic, implying a lot of work – and time…
1 Like
I had a look at the buidler code and I think it’s not worth optimizing at this point in time. When I have a bit more free time however I plan to explore the code deeper and hopefully contribute a bit :). Have a nice day!
I indeed think it’s questionable whether it’s worth the effort (and consider the time of the F-Droid team better invested in other areas) ![]()
1 Like