On 6 October 2015 at 19:03, Michael Wood <[email protected]> wrote:
> Make sure we associate build data with the built recipe rather than > toaster's configuration copy of the recipe. > What difference does this make to Toaster's behaviour? (I'm just asking so I can check the patch.) Thanks. Elliot > > Signed-off-by: Michael Wood <[email protected]> > --- > bitbake/lib/bb/ui/buildinfohelper.py | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/bitbake/lib/bb/ui/buildinfohelper.py > b/bitbake/lib/bb/ui/buildinfohelper.py > index 793418a..9195584 100644 > --- a/bitbake/lib/bb/ui/buildinfohelper.py > +++ b/bitbake/lib/bb/ui/buildinfohelper.py > @@ -285,6 +285,7 @@ class ORMWrapper(object): > > update_recipe_obj(recipe) > > + built_recipe = None > # Create a copy of the recipe for historical puposes and update it > for built_layer in self.layer_version_built: > if built_layer.layer == > recipe_information['layer_version'].layer: > @@ -300,7 +301,7 @@ class ORMWrapper(object): > if created and must_exist: > raise NotExisting("Recipe object created when expected to > exist", recipe_information) > > - return recipe > + return built_recipe > > def get_update_layer_version_object(self, build_obj, layer_obj, > layer_version_information): > if isinstance(layer_obj, Layer_Version): > -- > 2.1.4 > > -- > _______________________________________________ > toaster mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/toaster > -- Elliot Smith Software Engineer Intel Open Source Technology Centre
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
