**** BEGIN LOGGING AT Fri Mar 27 02:59:57 2020 Mar 27 10:29:25 in bblayers.conf, we need to specify the paths to meta layers; is there a way to get that a path relative to the directory `poky` is in, so that my bblayers.conf file works regardless of where I put the build directory? Mar 27 10:29:53 so that, for example, both `source poky/oe-init-build-env ../build` and `source poky/oe-init-build-env ./build` will work with the same bblayers.conf file Mar 27 10:35:04 mort, I use ${TOPDIR} Mar 27 10:36:04 mort, that is, I reference all my layers in bblayers.conf relative to ${TOPDIR} Mar 27 10:36:24 kroon: that points to the build directory, right? So it would be different depending on if I do `source poky/oe-init-build-env ./build` or `source poky/oe-init-build-env ../build` Mar 27 10:38:13 in my case, I have a `yocto` directory with `yocto/poky`, `yocto/meta-openembedded`, `yocto/meta-(our meta layer)`, etc. and want a variable which always points to that `yocto` directory regardless of where I put the build directory Mar 27 10:39:26 mort, ah ok. maybe find some other variable you can use as reference Mar 27 10:53:20 mort, COREBASE seems to point to openembedde-core path Mar 27 10:54:41 heh. but maybe that wont fly Mar 27 10:56:52 some fiddling with BB_CMDLINE perhaps Mar 27 11:37:43 <_inisider> hi. i have a question. is it a way to print all recipes which depends on interested recipe? just grep RDEPENDS in all layers? Mar 27 12:14:12 <_inisider> and i have one more question. what will happen if I have 2 bb files inside a folder and PREFERRED_PROVIDER is not set? Like here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-containers/docker?h=zeus Mar 27 12:19:45 _inisider: higher version takes precendence, unless defined otherwise somewhere AFAIK Mar 27 12:39:05 <_inisider> LetoThe2nd how it will understand in this case becuase as u can see there is no version in a recipe name? will it parse both bb files and compare PV variables? Mar 27 12:39:58 _inisider: i didn't look at the very incarnation, but yes, thats how i assume it to be. Mar 27 12:40:19 <_inisider> LetoThe2nd thanks Mar 27 12:43:10 _inisider: grep for RDEPENDS does only work for some of the runtime dependencies. Mar 27 12:43:42 <_inisider> how than do better? Mar 27 12:44:04 bitbake -g may help you Mar 27 12:44:52 <_inisider> but it will show the depencies of current recipe. Mar 27 12:44:58 Yes. Mar 27 12:45:43 <_inisider> but i want to know who depends on my "current" recipe Mar 27 12:45:56 grep DEPENDS also shows build-time dependencies. Mar 27 12:46:22 -also Mar 27 16:39:51 anyone else having issues compiling qwt-qt5 with master? Mar 27 16:51:13 Crofton|road: you can use dunfell if you don't need 5.15 Mar 27 16:52:12 ah qt-5.15? I was working on something to track master, but I could just make something to track dunfell instead Mar 27 16:53:20 Thanks for the tip, I will look at that after I ride the bicyle, going nuts in here today Mar 27 16:53:35 PC had a stick of ram flake out that was making me nuts Mar 27 17:41:53 is that a way of saying you are having memory problems ; ) Mar 27 18:08:25 heh Mar 27 18:15:21 I am still running on 4k core memory Mar 27 18:16:06 on 4004 intel cpu Mar 27 18:19:29 damn it going for a ride Mar 27 18:55:43 <_inisider> is it way by means of bitbake to verify which one recipe is used? bitbake -e virtual/kernel | grep PN and than grep for found name in a layers folder? Mar 27 18:57:25 bitbake -e virtual/kernel | grep '^FILE=' Mar 27 18:58:10 <_inisider> thanks **** ENDING LOGGING AT Sat Mar 28 02:59:59 2020