**** BEGIN LOGGING AT Mon Apr 29 02:59:56 2019
Apr 29 06:27:17 <Tofe> o/
Apr 29 06:59:15 <JaMa> morning
Apr 29 06:59:35 <JaMa> sorry I didn't get to testing your fix yet, burried deep in yocto upgrade :/
Apr 29 07:01:57 <Tofe> JaMa: no pb :)
Apr 29 07:02:31 <Tofe> Speaking of which, do you know if there are news about compiling Mesa with Meson?
Apr 29 07:04:36 <JaMa> Tofe: it should be merged soon
Apr 29 07:04:49 <JaMa> there is review on oe-core ML, it was already prepared before warrior
Apr 29 07:04:59 <JaMa> but postponed because of risks and now on it's way to master
Apr 29 07:05:30 <Tofe> I saw a mail about it on Mesa 18 yes, and they said they'd wait for Mesa 19 (makes sense), but then I didn't see anything new
Apr 29 07:05:55 <Tofe> Anyway, it's a detail
Apr 29 07:06:06 <Tofe> (might be a useful detail, one day... )
Apr 29 07:06:51 <JaMa> http://lists.openembedded.org/pipermail/openembedded-core/2019-April/281595.html
Apr 29 07:08:00 <JaMa> http://lists.openembedded.org/pipermail/openembedded-core/2019-April/281646.html should unblock it
Apr 29 07:09:16 <Tofe> ok great, thanks
Apr 29 07:09:37 <Tofe> anyway, that's mainly with Lima in mind, which won't be useful before Linux 5.2
Apr 29 07:11:56 <Herrie|Laptop> Morning!
Apr 29 07:12:25 <Herrie|Laptop> Seems the Voicecall PR is being reviewed now
Apr 29 07:12:56 <Tofe> ah great
Apr 29 07:18:37 <Tofe> the last comment (about having per-functionality flag instead of per-target) is not surprising to me, and I kind of agree, though it means quite a rework of the patch
Apr 29 07:19:54 <Herrie|Laptop> I thought that initially as well, then I decided, well it's all Mer/Nemo specific
Apr 29 07:20:03 <Herrie|Laptop> So lets use one
Apr 29 07:20:05 <Herrie|Laptop> But can split it
Apr 29 07:20:08 <Herrie|Laptop> Not so much work
Apr 29 07:25:27 <Herrie|Laptop> All the logics is already there yet, that was the hardest part to get in ;)
Apr 29 07:26:24 <Tofe> true :)
Apr 29 07:32:16 <Herrie|Laptop> PR was more to get their feedback. Can always tweak a bit. Just I prefer to keep these multi-file patches away where possible. Easy enough to solve it like this and Mer guys are reasonable usually ;)
Apr 29 07:37:50 <Herrie|Laptop> So thought to upstream it, saves us the hassle to update the patch all the time ;)
Apr 29 07:56:55 <Tofe> Of course, I completely agree
Apr 29 11:20:06 <Herrie|Laptop> Tofe: I guess this is more what they're after: https://git.merproject.org/Herrie/voicecall/commit/389e922927ee9c0e704eed9b9d3a3ed2484efc30
Apr 29 11:27:13 <Tofe> Herrie|Laptop: let's just see if they'd prefer having "with-ngf" instead of "no-ngf" :p
Apr 29 11:27:36 <Tofe> But having the current behavior as the baseline should please them I think
Apr 29 11:44:00 <Herrie|Laptop> Yeah seems so
Apr 29 11:46:12 <Herrie|Laptop> It builds OK at my side now as well. Needed to play around a bit with the .pro files, but got it working with not too much effort
Apr 29 13:05:48 <Herrie|Laptop> Tofe: Not a big fan of the !no-ngf followed by no-ngf but I don't really see how I could work around this. I need to have a DEFINED based on the flag to work some magic inside the .cpp/h files ;) https://git.merproject.org/mer-core/voicecall/merge_requests/19/diffs#a70f45ecb0cdb151525c8793fa4a101c1746d51c
Apr 29 14:07:02 <Tofe> you could use "else"
Apr 29 14:07:18 <Tofe> no-ngf { blabla } else { blibli }
Apr 29 14:07:38 <Tofe> it's also a double negation, but less visible...
Apr 29 15:12:49 <Herrie|Laptop> OK reworking & testing a bit
Apr 29 15:21:07 <Herrie|Laptop> Seems to build fine now, so up to Mer guys to check at their end
Apr 29 16:33:56 <Herrie|Laptop> Tofe: Can confirm VBox now also behaves at my end
Apr 29 16:34:48 <Tofe> ok, great !
**** ENDING LOGGING AT Tue Apr 30 02:59:57 2019