Created attachment 1445 [details] python trace call master:2051e4dff4384e1b618a050aeebf72a76cadab4b 1) clone poky master 2) source the build environment 3) change current directory to build/conf 4) issue command "bitbake man" Notice Python trace call (see attached)
After talked with Paul E, it seems that we had two methods to fix it: 1) Change the include conf/local.conf to require con/local.conf Or 2) Add a check for CONF_VERSION in sanity.bbclass, sys.exit(1) if it is None, but this is a little late since the cache, sstate-cache and tmp-eglibc dirs would be created in the conf dir.
(In reply to comment #1) > After talked with Paul E, it seems that we had two methods to fix it: > > 1) Change the include conf/local.conf to require con/local.conf > For the way 1, the problem is that there maybe really a loca.conf, but we are just looking for it in the wrong place. > Or > > 2) Add a check for CONF_VERSION in sanity.bbclass, sys.exit(1) if it is None, > but this is a little late since the cache, sstate-cache and tmp-eglibc > dirs > would be created in the conf dir.
RP's Patch, and the document needs update: http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/wip76 this means we'd now support: a) running bitbake xxx anywhere within a build directory (the first patch) b) running bitbake xxx anywhere at all if BBPATH is set to the build directory
Test cases created: https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=789 https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=790 Will add them to future master branch Test Runs
Resolved with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c7a389729a5453bf090f05946bfa64413a5e04ed
Verified in: poky master:2f64fae60b3f61a2c45dc9e5314d2d16b1e64605
Hi, I am not convinced that we need to change the documentation for this bug. Right now, we specify that TOPDIR points to the build directory. Within the documentation set, we do not restrict the user to being in any specific directory when they run the 'bitbake' command. I am going to mark the docs as not needed here. Scott
Hi, After talking with Corneliu about this bug it was decided a small documentation change for the BBPATH variable was in order. I added a note to the definition stating that if you run bitbake from outside the build directory, you need to have BBPATH set to point to the build directory. You can see the change here - http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#var-BBPATH I updated the doc requirement to "done". Scott