**** BEGIN LOGGING AT Fri Dec 08 03:00:02 2017 Dec 08 09:14:37 Hello. We are on pyro. I just wanted to know if there is some planned support for the meson build system with the SDK. As you may know the meson build system expects the default compiler to be available (to run some tests), so it doesn't accept environments with overriden environment variables for the compiling tools (CC, CXX, AR, STRIP, ...). Dec 08 09:15:20 Meson uses cross-files that define the cross-compilation. I have been generating them from a sourced environment: https://github.com/RafaGago/base_library/blob/master/build_helpers/meson-crossfile-from-yocto-sdk-env.sh Dec 08 09:22:31 rgc: i'm not into the details, but i've seen a lot of meson patches flowing through. so my first guess would be that things are still expanding in functionality, but that will probably not be backported to pyro, at least not in upstream. Dec 08 09:28:02 LetoThe2nd: Good to hear that thing are moving, as meson is gaining a lot of traction. Thanks for answering! Dec 08 09:28:31 rgc: personally i would suggest to have a look at the current head. Dec 08 09:30:33 meson was available in meta-oe for pyro & rocko, moved to oe-core during the current dev cycle Dec 08 09:31:05 https://layers.openembedded.org/layerindex/branch/pyro/recipes/?q=meson Dec 08 11:18:06 joshuagl: Thank you Dec 08 11:20:42 i'm trying to understand why the networkmanager recipe depends on mozjs (the javascript engine). I can't find any DEPENDS in the recipe, neither in the main DEPENDS, nor in any of the enabled PACKAGECONFIGs. In fact, The only mention of mozjs I see in the entire output of bitbake -e networkmanager is "SECURITY_CFLAGS_pn-mozjs="\${SECURITY_NO_PIE_CFLAGS}" .. anyone know how I can figure out where this dependency Dec 08 11:20:44 comes from? I know it's a dependency because a) mozjs gets included in the rootfs and b) it's listed as a NM dependency when i run bitbake -g networkmanager and look into recipe-depends.dot Dec 08 11:21:58 according to the NM devs, NM does not have a dependency on mozjs Dec 08 11:24:03 (im using the standard NM recipe that ships with meta-openemedded) Dec 08 11:33:24 also, how can i find out what recipe installed a certain file in my image rootfs? just searching all workdirs for the file won't work if the package was built from sstate (and doesn't have the file unpacked in its $WORKDIR) Dec 08 11:33:51 mago1: I'm pretty sure polkit uses mozjs, perhaps use taskexp to verify? Dec 08 11:34:51 joshuagl: yeah, polkit does rely on mozjs according to taskexp. but so does networkmanager (also according to taskexp) Dec 08 11:40:08 to find which recipe installed a file use `oe-pkgdata-util find-path /path/to/file` Dec 08 11:49:47 cool, thanks! **** ENDING LOGGING AT Sat Dec 09 03:00:00 2017