<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Feb 18, 2016 at 7:19 AM Markus Lehtonen <<a href="mailto:markus.lehtonen@linux.intel.com">markus.lehtonen@linux.intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Create config fragment if the user makes modifications to kernel config.<br>
User may change .config e.g. by directly editing it or by running the<br>
'do_menuconfig' bitbake task. Devtool generates one monolithic fragment<br>
by simply doing a diff between .config and .config.baseline files in the<br>
source directory. If either of these files is missing, the config<br>
fragment is not gerenrated or updated. The output is a file,<br>
'devtool-fragment.cfg' that gets added to SRC_URI in the recipe (as well<br>
as copied into the 'oe-local-files' directory if that is present in the<br>
source tree).<br>
<br>
${S}/.config will be a symlink to ${B}/.config. We need to do this as<br>
devtool is not able to access ${B} because ${B} is set in a .bbappend in<br>
the workspace layer which is not parsed by devtool itself.<br>
<br>
[YOCTO #8999]<br>
<br>
Signed-off-by: Markus Lehtonen <<a href="mailto:markus.lehtonen@linux.intel.com" target="_blank">markus.lehtonen@linux.intel.com</a>><br></blockquote><div><br></div><div>If the devtool-fragment.cfg already exists, what's the behavior? Will it update it with both the old and new changes, or will it create a second fragment?</div></div></div>