11402 2017-04-21 21:32:20 +0000 Refkit: Error when sourcing refkit-init-build-env outside of intel-iot-refkit directory tree 2017-05-17 19:04:06 +0000 1 1 6 Yocto Project Subprojects IoT Reference OS Kit intel-iot-refkit-tools 2.3 x86 Multiple RESOLVED FIXED Medium normal 2.4 M1 1 henry.bruce mikko.ylinen brian.avery --- --- Don't know oldest_to_newest 72771 0 henry.bruce 2017-04-21 21:32:20 +0000 'source refkit-init-build-env' fails when run outside of intel-iot-refkit directory tree Steps to re-create ------------------- $ cd ~ $ mkdir work $ git clone --recursive https://github.com/intel/intel-iot-refkit.git $ cd ~/work $ source ~/intel-iot-refkit/refkit-init-build-env Error: The bitbake directory (/home/hbruce/work/bitbake) does not exist! Please ensure a copy of bitbake exists at this location or specify an alternative path on the command line Contrast to behavior with poky ------------------------------- $ cd ~ $ mkdir work $ git clone https://git.yoctoproject.org/git/poky $ cd ~/work $ source ~/poky/oe-init-build-env You had no conf/local.conf file. This configuration file has therefore been created for you with some default values. ... You can also run generated qemu images with a command like 'runqemu qemux86' 72828 1 henry.bruce 2017-04-25 14:33:40 +0000 As poky allows build workspace to be in a different directory tree from the meta-data, developers will expect this behavior to be supported by RefKit even though it is not the documented procedure. People to hit this issue so far include Brian Avery (Intel) and Khem Raj (Comcast). If bug is not addressed this number will grow over time. 73108 2 mikko.ylinen 2017-05-08 11:06:34 +0000 A fix submitted: https://github.com/intel/intel-iot-refkit/pull/149 73139 3 mikko.ylinen 2017-05-09 12:16:06 +0000 (In reply to comment #2) > A fix submitted: https://github.com/intel/intel-iot-refkit/pull/149 Henry, Brian: can you please give the review feedback. 73298 4 mikko.ylinen 2017-05-17 19:02:58 +0000 The fix is now merged 73299 5 mikko.ylinen 2017-05-17 19:03:34 +0000 The fix is now merged