**** BEGIN LOGGING AT Mon Nov 06 03:00:02 2017
Nov 06 18:18:45 <Crofton|work> should rocko run without python2 on build machine?
Nov 06 18:19:05 <otavio> Crofton|work: I hope it does
Nov 06 18:19:13 <otavio> Crofton|work: but AFAIK eSDK does not
Nov 06 18:19:29 <Crofton|work> [balister@prague rocko]$ TEMPLATECONF=`pwd`/meta-sdr/conf source ./openembedded-core/oe-init-build-env ./build ./bitbake
Nov 06 18:19:29 <Crofton|work> bash: python: command not found...
Nov 06 18:19:29 <Crofton|work> Install package 'python2' to provide command 'python'? [N/y] N
Nov 06 18:19:49 <otavio> eheh
Nov 06 18:20:20 <Crofton|work> something funny is there
Nov 06 18:20:37 <otavio> Crofton|work: I'd say broken, not funny ;-P
Nov 06 18:22:01 <Crofton|work> true
Nov 06 18:23:30 <JaMa> @prague? :)
Nov 06 18:25:59 <Crofton|work> ERROR: The following required tools (as specified by HOSTTOOLS) appear to be unavailable in PATH, please install them in order to proceed:
Nov 06 18:25:59 <Crofton|work>   chrpath diffstat g++ makeinfo patch python python2 python2.7
Nov 06 18:26:03 <Crofton|work> lol new machine
Nov 06 18:26:10 <Crofton|work> named after last ELC* town
Nov 06 18:43:11 <jeroen> hi, I made a workaround to use the meta-toolchain-qte SDK directly from Qt Creator (so without having to source the env script)...
Nov 06 18:44:10 <jeroen> Is that useful for meta-qt5 itself or is everybody happy with source the script..
Nov 06 18:44:51 <otavio> jeroen: sure; it is
Nov 06 18:45:00 <otavio> jeroen: specially if it is a generic fix
Nov 06 18:45:24 <jeroen> otavio: for my case it is here, https://github.com/victronenergy/meta-victronenergy/commit/e9071419e9ba0602a1140a5ce84c005947a46d68
Nov 06 18:45:42 <jeroen> but it can be made more generic / optional e.g.
Nov 06 18:47:08 <otavio> jeroen: sure; I think it can also be changed to avoid its need. If it uses the right pattern the relocating script will do it for you
Nov 06 18:47:27 <otavio> jeroen: or it can be done as a post-environment hook
Nov 06 18:48:26 <otavio> jeroen: it can also be included in the populate_sdk_qt5.bbclass so it is used 
Nov 06 18:49:08 <jeroen> yes, there are multiple ways to do it, this is the make it work for me version and let meta-qt5 do its own thing version..
Nov 06 18:49:57 <otavio> jeroen: I think for meta-qt5, I'd try to use the @PATTERN@ so it i done by the normal script
Nov 06 18:51:01 <otavio> jeroen:  if you want to look at it, I can review it first prior posting
Nov 06 18:56:24 <jeroen> yes, I am fine with spending some time on it, since I like to see it "fixed" in upstream.. It is not really broken, but it is e.g. not possible to easily switch between qt4 / qt5 without having multiple qtcreator instances
Nov 06 18:57:57 <jeroen> On the other hand I don't know SDK internals without looking into it, so you will have to be a bit patient with me I guess...
Nov 06 19:00:04 * jeroen googling for post-environment hook
Nov 06 19:04:02 <otavio> jeroen: that's fine
Nov 06 19:04:52 <jeroen> ok, lets check first if I understand correctly what meta-qt5 is doing...
Nov 06 19:05:01 <otavio> jeroen: the best solution is to make it use expanded vars when creating the qmake config  so the relocation script does it magic
Nov 06 19:05:22 <otavio> jeroen: the post-env would require you to source once
Nov 06 19:05:56 <otavio> jeroen: to do use telegram or hangouts?
Nov 06 19:06:09 <otavio> easier to talk to me
Nov 06 19:07:40 <jeroen> no, but I will have a look what they are and contact you there.. (likely tomorrow)
Nov 06 19:09:37 <otavio> jeroen: in this case, talk to me here
Nov 06 19:09:41 <otavio> it is fine
Nov 06 19:10:16 <jeroen> otavio: short question for now though, do you have a link for what post-env is? I get the first part, but not this one..
Nov 06 19:12:54 <otavio> jeroen: sure; hold on
Nov 06 19:14:15 <otavio> jeroen: http://termbin.com/lxud
Nov 06 19:16:11 <jeroen> otavio: ah that one, they are sourced indirectly by my patch, since the complete env is sourced
Nov 06 19:16:31 <jeroen> see, https://github.com/victronenergy/meta-victronenergy/commit/e9071419e9ba0602a1140a5ce84c005947a46d68#diff-f34aa3670e480a599edf736f9a286b63R15
Nov 06 19:17:25 <jeroen> (I am on jethro btw.., so things might have changed)
Nov 06 19:22:13 <otavio> jeroen: sure
Nov 06 19:22:47 <otavio> jeroen: but do you see what I am suggesting? it is not to use this but instead use full variable
Nov 06 19:23:26 <jeroen> I am purposely ignoring that one, since qt5 only needs a valid compiler and their flags (and hence the sysroot location after install). moc and friends are known from qmake.conf
Nov 06 19:23:27 <jeroen> anyway, I will contact you over your preferred medium later, so we can discuss it without bothering all others..
Nov 06 21:18:17 <Crofton|work> fischerm, can uhd build with python3?
Nov 06 21:18:51 <armpit> Crofton|work, you know he just going to say yes, just to mess with you
Nov 06 21:18:59 <Crofton|work> heh
Nov 06 21:19:20 <Crofton|work> He is whining about py2 mako going away
Nov 06 21:20:10 <armpit> Real German's don't whine
Nov 06 21:48:55 <Crofton|work> Did anyone get any OEDEM photos?
Nov 06 21:51:59 <armpit> what happens in OEDEM stays in OEDEM
Nov 06 21:52:08 <georgem> heh
Nov 06 22:22:08 <bluelightning> armpit: one more thing - https://patchwork.openembedded.org/patch/144511/ doesn't seem to be in pyro or your next branch though it's marked accepted
Nov 06 22:25:13 <armpit> shoot.. had some filters incorrectly set. now I see it
Nov 06 23:24:09 <bluelightning> armpit: ok, no worries
Nov 07 01:30:31 <armpit> JaMa, I pushed patches to stagging/master-next. let me know when i can kick off a world build
**** ENDING LOGGING AT Tue Nov 07 03:00:02 2017