[yocto] Deleting layers in Hob

Xu, Dongxiao dongxiao.xu at intel.com
Thu Mar 29 05:00:10 PDT 2012


On Thu, 2012-03-29 at 19:05 +0800, Barros Pena, Belen wrote:
> Hi all,
> 
> Do we have enough information to make a decision about the meta-yocto
> layer? I don't understand all the technical details, but I am inclined to
> make it non-deletable in Hob (i.e. it is not possible to delete this layer
> in Hob).

The layer is removable in Hob, since many people are just using oe-core
without meta-yocto layer.

I have patches to solve the deletion of meta-yocto layer, and will send
it out soon.

Thanks,
Dongxiao

> 
> What do you think?
> 
> Belen
> 
> On 27/03/2012 17:56, "Joshua Lock" <josh at linux.intel.com> wrote:
> 
> >On 27/03/12 00:19, Lu, Lianhao wrote:
> >>
> >>> -----Original Message-----
> >>> From: yocto-bounces at yoctoproject.org
> >>>[mailto:yocto-bounces at yoctoproject.org] On Behalf Of Xu, Dongxiao
> >>> Sent: Tuesday, March 27, 2012 2:49 PM
> >>> To: yocto
> >>> Subject: [yocto] Deleting layers in Hob
> >>>
> >>> When using Hob in Yocto Project, I found a issue when deleting layers.
> >>>I
> >>> think I ever raised this problem before.
> >>>
> >>> Let me briefly introduce how layer removal works in Hob. When user
> >>> changes a layer, it will following the below steps
> >>> 1) init the cooker.
> >>> 2) set new layers to cooker.
> >>> 3) parse configuration files.
> >>> 4) get available machines, distros, SDKs, etc.
> >>>
> >>> As we know, if we source oe-init-build-env in Yocto project
> >>>environment,
> >>> we will have DISTRO="poky" set in local.conf by default, where the
> >>> "poky" DISTRO comes from the meta-yocto layer. If user deletes
> >>> meta-yocto in Hob, and then error will happen when bitbake parsing the
> >>> local.conf, since it could not find where the "poky" DISTRO is defined.
> >>>
> >>> Even if we are able to successfully removed the meta-yocto layer by
> >>> removing the DISTRO definition in local.conf, system will report
> >>>another
> >>> issue that:
> >>>
> >>> Your configuration is using stamp files including the sstate hash but
> >>> your build directory was built with stamp files that do not include
> >>> this.
> >>> To continue, either rebuild or switch back to the OEBasic signature
> >>> handler with BB_SIGNATURE_HANDLER = 'OEBasic'.
> >>>
> >>> This is because BB_SIGNATURE_HANDLER = "OEBasic" is also defined in
> >>> meta-yocto layer (poky.conf).
> >>
> >> Meta-yocto is using OEBasicHash as default signature
> >>handler(ABI_VERSION=8, see ${TMPDIR}/abi_version), while oe-core is
> >>still using the OEBasic(ABI_VERSION=7). This means the oe-core can not
> >>reuse the stamp files generated by meta-yocto.
> >
> >Could we workaround the incompatibility by setting BB_SIGNATURE_HANDLER
> >= "OEBasic" somewhere in meta-hob?
> >
> >Cheers,
> >Joshua
> >-- 
> >Joshua '贾詡' Lock
> >         Yocto Project "Johannes factotum"
> >         Intel Open Source Technology Centre
> >_______________________________________________
> >yocto mailing list
> >yocto at yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/yocto
> 





More information about the yocto mailing list