[OE-core] [PATCH v2 2/2] devtool: update-recipe: create config fragment

[Christopher Larson]

On Thu, Feb 18, 2016 at 7:19 AM Markus Lehtonen <
markus.lehtonen at linux.intel.com> wrote:

> Create config fragment if the user makes modifications to kernel config.
> User may change .config e.g. by directly editing it or by running the
> 'do_menuconfig' bitbake task. Devtool generates one monolithic fragment
> by simply doing a diff between .config and .config.baseline files in the
> source directory.  If either of these files is missing, the config
> fragment is not gerenrated or updated. The output is a file,
> 'devtool-fragment.cfg' that gets added to SRC_URI in the recipe (as well
> as copied into the 'oe-local-files' directory if that is present in the
> source tree).
>
> ${S}/.config will be a symlink to ${B}/.config. We need to do this as
> devtool is not able to access ${B} because ${B} is set in a .bbappend in
> the workspace layer which is not parsed by devtool itself.
>
> [YOCTO #8999]
>
> Signed-off-by: Markus Lehtonen <markus.lehtonen at linux.intel.com>
>

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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160218/bde0931e/attachment-0002.html>