**** BEGIN LOGGING AT Fri Mar 17 03:00:01 2017 Mar 17 05:10:48 who is working on the ext_sdk? Mar 17 05:11:00 i think i've found a small bug (but i haven't had time to confirm) Mar 17 05:11:53 when i "-c populate_sdk_ext" from a nodistro build (i.e. openembedded-core) the sysroots etc get put in tmp-glibc (i.e. tmp-${TCLIBCAPPEND}) Mar 17 05:12:12 but the environment file that gets shipped assumes "tmp", so all the $PATHs are off Mar 17 11:58:33 tlwoerner: paul is the overall owner right now Mar 17 12:20:44 anyone tried packaging wine in OE? i need it to generate python2exe binaries for windows Mar 17 12:25:15 (yeah, i know how silly it sounds...) Mar 17 12:30:21 doesn't sound silly at all :) Mar 17 12:30:44 layer index says nobody has published a wine recipe though Mar 17 12:35:17 I've heard so many silly ideas over the years, nothing surprises me anymore Mar 17 12:37:43 mago1: there's a meta-mingw layer that builds windows cross-compilers, so packaging wine isn't silly at all ;) Mar 17 12:41:02 it feels silly to package wine into the build system just so that i can produce an EXE file of my python scripts. Just because my users can't be bothered with running python on their own Mar 17 13:01:21 mago1: you can look at gentoo ebuild to get some start point Mar 17 13:01:24 https://github.com/gentoo/gentoo/tree/520c3860f105190ace3d0cf26c6699f5d728ef9f/app-emulation/wine Mar 17 13:13:16 thanks Mar 17 15:23:57 if i do mktemp in a native recipe, will that create a tempdir outside my buildtree? Mar 17 15:27:48 berton: huh, so that's how the pros do it, eh? ;-) Mar 17 15:29:28 mago1: mktemp is a system tool, not an oe one Mar 17 15:29:49 but mktemp lets you specify whether you want it to be in /tmp or an arbitrary location Mar 17 15:29:51 so that's really up to you Mar 17 15:29:53 read the man page Mar 17 15:30:00 kergoth: cool, thanks Mar 17 15:30:18 np **** ENDING LOGGING AT Sat Mar 18 03:00:01 2017