Bug 8211 - toaster is searching for toasterconf.json in unacceptable places.
Summary: toaster is searching for toasterconf.json in unacceptable places.
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Low minor
Target Milestone: 2.1
Assignee: brian avery
QA Contact: Libertad
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-08-26 19:30 UTC by brian avery
Modified: 2016-04-25 17:51 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brian avery 2015-08-26 19:30:18 UTC
Toaster is searching outside of the git tree for the configuration file.
To reproduce:
~/cow/poky1 
~/cow/poky-contrib

This is where we run toaster:
~/cow/toaster-run/
TOASTER_MANAGED=1 TOASTER_DEVEL=1  ../poky/bitbake/bin/toaster

We get:
Toaster will list now the configuration files that it found. Select the number to use the desired configuration file.
  [1] /home/bavery/cow/poky1/meta-yocto/conf/toasterconf.json
  [2] /home/bavery/cow/poky-contrib/meta-yocto/conf/toasterconf.json

  [0] - Exit without importing any file

The problem:
Toaster shouldn't be searching nearby directories for the configuration file especially since the other directory could be a checkout/branch of anything.
Comment 1 Phlip Balister 2016-04-11 14:39:42 UTC
I use a setup with bitbake and oe-core checked out at the same level, I just want to mention that toaster cannot assume that is is running with poky.
Comment 2 brian avery 2016-04-11 21:01:43 UTC
This patch (now in master) should fix that issue, at least. 
http://lists.openembedded.org/pipermail/openembedded-core/2016-April/119997.html
Comment 3 Belen Barros Pena 2016-04-25 14:42:03 UTC
According to Michael Wood, this is probably fixs, "as you can now specify TOASTER_CONF"
Comment 4 brian avery 2016-04-25 17:51:11 UTC
And we now use TEMPLATECONF to determine the correct conf directory from which to load the file. This is the same mechanism that oe-init-build-env uses.