**** BEGIN LOGGING AT Fri Jul 07 03:00:03 2017 Jul 07 13:13:08 hey all, I've got a recipe I'm building for nativesdk that depends on x11 but I'd like to have it assume that this is provided on my sdk host...I've tried adding to ASSUME_PROVIDED but it's not working..I was wondering if that ASSUME_PROVIDED only works in the normal use case of build host native packages or if there's some alternative way to use the sdk host's x11 packages. Jul 07 13:18:31 what are you adding to assume provided? Jul 07 13:20:56 a good question is why not just use nativesdk-libx11? Jul 07 13:21:36 nativesdk-libx11 nativesdk-libxext nativesdk-libxrender nativesdk-libxrandr Jul 07 13:22:10 well, good question, a follow-on was going to be if the recommended path is to just build all that into the SDK. Jul 07 13:22:48 yeah its easier :) Jul 07 13:23:25 ok then, I like easy :) I was wondering if there were dragons down this other path. Jul 07 13:23:47 ASSUME_PROVIDED+=nativesdk-libx11 should just work though Jul 07 13:25:40 well, I should add that there's a twist here...my DISTRO_FEATURES does not have x11 (target is wayland-based) so I'm already overriding an assumption in libsdl that the nativesdk version should be configured based on DISTRO_FEATURES (not a good assumption for an SDK) Jul 07 13:26:02 so maybe that's the end issue..I did notice: Jul 07 13:26:06 ERROR: nativesdk-libxext was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES) Jul 07 13:28:02 i wonder if DISTRO_FEATURES_NATIVESDK was in pyro or just master Jul 07 13:28:43 yeah pyro has it Jul 07 13:28:50 upgrade to the latest release and that problem is solved :) Jul 07 13:28:53 ahh, that pointer alone helps me, though sadly we're not on pyro yet Jul 07 13:28:59 +DISTRO_FEATURES_NATIVESDK ?= "x11 libc-charsets libc-locales libc-locale-code" Jul 07 13:28:59 hehe, of course Jul 07 13:29:57 ok, thanks, looks exactly like what I need. Jul 07 14:45:24 mdp, how is the heartland? Jul 07 14:58:46 Crofton|work: great when experienced from 35k feet, right? Jul 07 14:59:02 heh Jul 07 14:59:19 All is well, vacation next week. How is the south? Jul 07 14:59:26 Humid Jul 07 14:59:33 +1 Jul 07 14:59:33 I'm on vactoin next weeks also Jul 07 14:59:46 Sailed by the boy scout camp last weekend Jul 07 15:00:47 Aha, we loved that BRSR..great camp. We'll be down at a campground on the new river next week Jul 07 15:01:04 where at? Jul 07 15:01:18 Although I'll be headed for the Pacific Jul 07 15:01:40 ACE Adventure "resort"..guess that's Minton, WV Jul 07 15:01:47 Crofton|work: your vacation sounded like bitcoin :) Jul 07 15:02:11 Busy week of kayaks, duckies, rafts, climbing Jul 07 15:02:22 Hinton? Jul 07 15:03:12 No sorry, oak hill Jul 07 15:04:07 NRV Gorge bridge area Jul 07 15:04:26 Yeah Jul 07 15:06:25 Eager to run the Gauley this time Jul 07 15:07:23 never done that, have rapelled gorge bridge though Jul 07 15:08:03 Cool. Jul 07 15:09:36 Guess I'll see you in Prague next Jul 07 15:10:42 Hope so! Jul 07 15:14:26 I predict we'll have beers..my crystal ball is infallible. Jul 07 19:42:40 khem: how does devtool know where to extract recipe changes to? Jul 07 19:43:24 nm, should read the excellent help: --append Jul 07 19:45:20 devtool update-recipe --append sources/meta- kernel-recipe Jul 07 19:45:23 wow, it just worked Jul 07 19:46:39 * cbrake cleans resets recipe in workspace and sees what it does with patches ... Jul 07 19:53:21 yeah devtool finish Jul 07 19:53:25 is what I use Jul 07 19:55:46 and re-setting up the workspace, devtool applies your patches in git: https://gist.github.com/cbrake/9e80e7b8ad51a704b5ab314a57694e28 Jul 07 19:56:03 so devtool+git is the new quilt Jul 07 19:56:19 right Jul 07 19:56:52 with a tool to guide the workflow Jul 07 19:57:07 onoffon: yup, very impressive Jul 07 19:57:36 cbrake this is onoffon=khem btw. Jul 07 19:57:53 on laptop I use onoffon Jul 07 20:30:47 hey guys Jul 07 20:32:13 someone around who knows altera SoCs and sopc2dts tool? Jul 07 20:55:38 blight: whats your question Jul 07 20:55:54 * cbrake really appreciates qt5 will now build with a bunch of opengl crud being in place ... Jul 08 01:07:30 just measured chromium linking spent ~8 mins and used up 14.7 GB ram Jul 08 01:07:54 so folks know what kind of machine they would need Jul 08 01:08:06 i will see if I can get numbers with gold Jul 08 01:08:10 needs twice that to actually run it Jul 08 01:08:19 jk ;) **** ENDING LOGGING AT Sat Jul 08 03:00:00 2017