**** BEGIN LOGGING AT Sun Jul 16 03:00:01 2017 Jul 16 08:13:04 Morning! Jul 16 09:01:33 Morning! Jul 16 09:08:05 Herrie: you know JaMa already did some work related to Qt 5.7/5.8, right ? Jul 16 09:08:22 https://github.com/webOS-ports/qtwebengine-chromium/commits/webOS-ports/master-next Jul 16 09:15:07 Tofe: That looks like an old one Jul 16 09:15:12 Commits are going back to 2016 Jul 16 09:15:19 ah, yes, right Jul 16 09:15:28 This one is what I did: https://github.com/webOS-ports/qtwebengine-chromium/commits/webOS-ports/master-53-based Jul 16 09:15:30 Should be fine Jul 16 09:15:38 In terms of code Jul 16 09:15:42 I didn't do a build test Jul 16 09:15:51 53-based = 5.8 Jul 16 09:15:56 56-based would be 5.9 Jul 16 09:16:02 anyway, there were some mistakes in yours, so I redid the cherry-pick, just to be sure Jul 16 09:16:56 Building qtwebengine takes much longer than redoing such rebsae :) Jul 16 09:19:28 Tofe: Hmmz :S Jul 16 09:19:37 I must have been low of coffee when I did it Jul 16 09:19:43 Looked pretty straight forward Jul 16 09:21:23 there were some 3-ways merges where coffee was a prerequisite Jul 16 09:22:45 anyway, the chromium part won't be much of a problem, it's the Qt wrapper that could take more time... I've done a first try, but I think I broke the Sync message send Jul 16 09:23:22 The syntax changed a lot, so I just don't know how it precisely works now :/ Jul 16 09:24:39 Herrie: also I've moved qtwayland.bbappend to also use patches, as almost all was fixed upstream Jul 16 09:35:24 Tofe: Nice to have a bbappend :) Jul 16 09:35:50 I noticed that the qt part changed a bit, but didn't look too drastical from what I could see? Jul 16 09:37:10 Herrie: for which code ? Jul 16 09:41:57 Tofe: The qtwebengine bits Jul 16 09:42:10 When I checked only the sync messages looked like it changed a bit Jul 16 09:43:50 Herrie: yes, that's right, but it changed quite a lot Jul 16 09:44:14 now it uses some kind of template, with (maybe) introspection, I don't know exactly Jul 16 09:44:41 Also the IDL interface has to be migrated; I tried something, we'll see if it works... Jul 16 10:06:10 Tofe: OK :) Jul 16 10:06:30 Well seeing it went from Chromium 45->53 it's not unexpected that there are some changes Jul 16 10:07:05 QT 5.9 goes to 56 it seems Jul 16 10:07:24 Also noticed that JaMa is quite some commits behind on 5.8 upstream it seems Jul 16 10:17:01 He's at https://github.com/meta-qt5/meta-qt5/blob/pyro/recipes-qt/qt5/qtwebengine_git.bb#L120 which is from 3rd of January Jul 16 10:17:56 About 50 commits Jul 16 10:18:03 Most don't seem very crucial Jul 16 10:18:18 But once you have it building with the current commit might be worth to bump Jul 16 11:13:30 Herrie: I've rebased on top of 5.8 already Jul 16 11:14:30 ah, wait, now I see what you mean Jul 16 11:14:43 well, let's just stick to meta-qt5 for the moment Jul 16 11:26:25 Tofe: Yeah looking at it there should be little that's very relevant for us Jul 16 15:38:11 JaMa: when you'll be around, maybe you could help me with this bitbake error: qtubuntu-camera Jul 16 15:38:14 https://paste2.org/tmg4xP2Z Jul 16 16:50:52 Tofe: Try adding RRECOMMENDS = libpulse-simple-dev Jul 16 16:52:11 Or even RRECOMMENDS_${PN} to be more specific Jul 16 16:52:59 You could try RDEPENDS_${PN} as well Jul 16 16:53:03 Either would work I guess Jul 16 16:53:15 Though RDEPENDS is a hard requirement and RRECOMMENDS more soft it seems Jul 16 17:24:15 no, there's nothing like that Jul 16 17:25:09 and the .pc is there, so I don't know what happens here Jul 16 18:11:37 Tofe: Hmmmz Jul 16 19:33:28 Tofe: I'll probably roll-back pidgin used for IM to 2.10.12. They removed various certs in the new release and gives issues for us it seems. Something to fix in the future I guess Jul 16 19:33:43 Just so stuff keeps working at least Jul 16 20:44:43 ok Jul 16 22:16:27 Tofe: Hmmz downgrade doesn't seem to solve it Jul 16 22:16:35 Must be something else then **** ENDING LOGGING AT Mon Jul 17 03:00:03 2017