**** BEGIN LOGGING AT Sat May 11 02:59:57 2019 May 11 13:49:28 how do I access environment variables from the yocto build environment May 11 13:49:49 is HOME in yocto the same as the HOME enironment variable? May 11 13:51:17 black_13: yes, but only a limited set of environment variables are allowed into the bitbake metadata to avoid contamination of the build May 11 13:51:34 that makes sense May 11 13:52:33 i wanted to find a way to locallize all the build and downloads to a directory and then delete this after a build May 11 13:52:39 but is this already done May 11 13:52:49 all the build products go to TMP May 11 13:54:04 black_13: There are already variables in Yocto that you can set to control where your build and your download directory are. May 11 13:54:20 there are May 11 13:55:42 TMPDIR DL_DIR SSTATE_DIR May 11 13:57:16 i would like to localize these under one root dir and then these could be deleted and the yocto script or build directory could be copied to another location and not be dependant on the path its copied into May 11 13:57:57 Sounds like you're trying to replicate sstate cache? May 11 13:58:05 Why don't you describe what your usecase is… May 11 13:58:26 sure May 11 14:01:02 path independence if performed a series of gits clones into a directory any directory and did bitbake configuration it would proceed and the resulting binaries would appear at a top level of that directory May 11 14:02:05 not sure if I understand you correctly, but isn't that already the case? May 11 14:02:27 it may be and i dont understand completely bitbake/yocto May 11 14:03:15 without setting it TMPDIR is under build directory May 11 14:03:35 the TMPDIR can be totally removed AFAIK May 11 14:04:18 Bitbake produces images and binary packages to be installed on the rootfs of (usually an) embedded system. The build path only affects that path baked into the debug symbols, and I'm not even sure it still does that in modern yocto. May 11 14:17:40 i have tried some games and it seems just leaving TMPDIR alone works out well May 11 14:24:31 the question i should ask is how to actually use the results of the build on a beagle machine May 11 14:24:54 I have been making images to run in qemu but never pulled the pin and flashed an image May 11 14:41:14 That's usually very board-specific, so it's hard to give a general answer. Consult your board's documentation. May 11 17:58:54 New news from stackoverflow: how can I define an IP adress to my SAMA5D27 Board? May 11 21:27:09 is the correct place to ask about beagle bone and yocto or just yocto May 11 22:49:56 how do build the deployable images May 11 22:50:59 or force the build for images May 12 00:25:35 black_13, https://github.com/beagleboard/meta-beagleboard May 12 00:26:05 seems pretty old May 12 00:29:52 yeah 6 years ago May 12 01:15:41 black_13, try http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/conf/machine May 12 01:16:43 Crofton_: i have been using https://jumpnowtek.com/beaglebone/BeagleBone-Systems-with-Yocto.html but nothing happens May 12 01:18:06 I'd start there and bug TI direct, not use old web pages **** ENDING LOGGING AT Sun May 12 03:00:31 2019