You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm quite new to using isar and bitbake but so far I found working with it a quite smooth experience.
However, I observed that the isar-setup-builddir script is only copying the content of bblayers.conf.sample and local.conf.sample to build/conf/.
See here
This will display an error message that the directory configured in .templateconf does not contain a local.conf file and also no bblayers.conf.
My naive assumption would be that I could provide a meta-isar/conf/local.conf right next to the meta-isar/conf/local.conf.sample and isar-setup-builddir would take this one instead and also not show the warning message.
Something like this:
if [ -r"$TEMPLATECONF/bblayers.conf"];then
ISARCORELAYERCONF="$TEMPLATECONF/bblayers.conf"else
ISARCORELAYERCONF="$TEMPLATECONF/bblayers.conf.sample"fi
Or is this a design decision because of how Bitbake works? I myself like the approach of just deleting the whole build folder and then let isar take care of copying the files to the right locations.
The text was updated successfully, but these errors were encountered:
protenhan
changed the title
isar-setup-builddir only loks for .sample files in TEMPLATECONF folder
isar-setup-builddir only looks for .sample files in TEMPLATECONF folder
Apr 29, 2019
I'm quite new to using isar and bitbake but so far I found working with it a quite smooth experience.
However, I observed that the isar-setup-builddir script is only copying the content of
bblayers.conf.sample
andlocal.conf.sample
tobuild/conf/
.See here
isar/scripts/isar-setup-builddir
Lines 69 to 70 in 596732a
This will display an error message that the directory configured in
.templateconf
does not contain a local.conf file and also no bblayers.conf.My naive assumption would be that I could provide a
meta-isar/conf/local.conf
right next to themeta-isar/conf/local.conf.sample
and isar-setup-builddir would take this one instead and also not show the warning message.Something like this:
Or is this a design decision because of how Bitbake works? I myself like the approach of just deleting the whole build folder and then let isar take care of copying the files to the right locations.
The text was updated successfully, but these errors were encountered: