Android SDK images to Qt 5.12

[Volker Krause]

On Friday, 22 February 2019 06:35:06 CET Ben Cooksley wrote:
> On Fri, Feb 22, 2019 at 8:46 AM Volker Krause <vkrause at kde.org> wrote:
> > On Saturday, 16 February 2019 19:45:03 CET Aleix Pol wrote:
> > > El ds., 16 de febr. 2019, 19:42, Ben Cooksley <bcooksley at kde.org> va
> > > 
> > > escriure:
> > > > On Sat, Feb 16, 2019 at 11:17 PM Volker Krause <vkrause at kde.org> 
wrote:
> > > > > On Thursday, 14 February 2019 09:09:57 CET Volker Krause wrote:
> > > > > > On Wednesday, 13 February 2019 16:28:20 CET Aleix Pol wrote:
> > > > > > > Hey,
> > > > > > > By popular demand, I updated our CI tooling to use the new
> > > > > > > images.
> > > > 
> > > > Many of
> > > > 
> > > > > > > you already tried them.
> > > > 
> > > > > > > It's building now as of:
> > > > https://build.kde.org/job/Administration/job/Docker%20Generate%20Andro
> > > > idQt
> > > > 
> > > > > > > 5. 12%20SDK
> > > > > > > 
> > > > > > > This means that we'll be changing compilers to clang too.
> > > > > > > 
> > > > > > > Some builds may fail, help will be welcome. ;)
> > > > > > 
> > > > > > Thanks a lot! Some of that breakage is caused by my changes, but
> > > > > > at
> > > > 
> > > > least I
> > > > 
> > > > > > can see it now again :) Will look into that ASAP.
> > > > > 
> > > > > Fixes for Konversation and KStars have been pushed too now, which
> > > > > leaves
> > > > > Marble and VVave. Those two seem to have issues unrelated to the
> > > > > image
> > > > 
> > > > change,
> > > > 
> > > > > and for the last time built successfully several months ago if I
> > > > > read
> > > > 
> > > > this
> > > > 
> > > > > correctly. So I think we finally have this all back under control :)
> > > > 
> > > > Given these two appear to be terminally broken, should we go ahead and
> > > > disable them for now until their respective maintainers/developers
> > > > have a chance to diagnose and fix the issue?
> > > > 
> > > > > Thanks,
> > > > > Volker
> > > > 
> > > > Cheers,
> > > > Ben
> > > 
> > > I talked with Camilo and he said he'd look into vvave build. Marble it's
> > > probably something we should look into rather than nuke?
> > 
> > Looked into this, it's caused by a combination of
> > KDE_L10N_AUTO_TRANSLATIONS being enabled and a double inclusion of
> > KDECMakeSettings.cmake, which duplicates the fetch-translation magic.
> > With any of those gone it builds fine.
> > 
> > That sounds easy to fix, however their build system seems to have ECM as
> > an
> > optional dependency (sic), which makes this rather messy.

Found an easy fix after all: https://phabricator.kde.org/D19223

> This optional nature of ECM causes other issues as well so this is
> something that should either:
> a) Be changed to make it non-optional
> b) Result in Marble being removed from Android builds

Not disagreeing with that.

Regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-android/attachments/20190222/eb0c4385/attachment.sig>