Re: [yocto] Building boost-python

[VanCutsem, Geoffroy]

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Jakob Hasse
> Sent: Wednesday, June 7, 2017 11:48 AM
> To: Yocto List 
> Subject: [yocto] Building boost-python
> 
> Hello,
> 
> One of my layers needs boost-python.
> When I try to build boost-python with bitbake, it complains:
> 
> ERROR: Nothing PROVIDES 'boost-python'
> 
> How can I fix this?
> Boost itself builds and I also included
> PACKAGECONFIG_pn_boost = "python"
> without any effect.

I believe the correct spelling is:
PACKAGECONFIG_pn-boost = "python"
(note the hyphen instead of underscore)

> 
> My bblayers.conf is here:
> 
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf #
> changes incompatibly LCONF_VERSION = "6"
> 
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
> 
> BBLAYERS ?= " \
>/usr/local/dey-2.0/sources/poky/meta \
>/usr/local/dey-2.0/sources/poky/meta-yocto \
>/usr/local/dey-2.0/sources/poky/meta-yocto-bsp \
>/usr/local/dey-2.0/sources/meta-openembedded/meta-oe \
>/usr/local/dey-2.0/sources/meta-openembedded/meta-python \
> /usr/local/dey-2.0/sources/meta-openembedded/meta-networking \
> /usr/local/dey-2.0/sources/meta-openembedded/meta-webserver \
>/usr/local/dey-2.0/sources/meta-qt5 \
>/usr/local/dey-2.0/sources/meta-swupdate \
>/usr/local/dey-2.0/sources/meta-fsl-arm \
>/usr/local/dey-2.0/sources/meta-fsl-demos \
>/usr/local/dey-2.0/sources/meta-digi/meta-digi-arm \
>/usr/local/dey-2.0/sources/meta-digi/meta-digi-dey \
>/usr/local/dey-2.0/sources/meta-java/ \
>/usr/local/dey-2.0/sources/meta-iot-cloud/ \
> 
>"
> BBLAYERS_NON_REMOVABLE ?= " \
>/usr/local/dey-2.0/sources/poky/meta \
>/usr/local/dey-2.0/sources/poky/meta-yocto \
>"
> 
> Any help is welcome!
> Jakob
> 
> --
> Jakob Hasse
> Software Developement
> 
> E: jakob.ha...@smart-home-technology.ch
> T: +41 44 552 02 66
> 
> Smart Home Technology GmbH
> www.smart-home-technology.ch
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Whats the better way to maintain the Yocto project for an embedded product - git submodules or repo or using Combo-layer

[VanCutsem, Geoffroy]

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Paul Barker
> Sent: Wednesday, January 18, 2017 11:09 AM
> To: yocto@yoctoproject.org; Eswaran Vinothkumar (BEG-PT/PJ-IOT1)
> 
> Subject: Re: [yocto] Whats the better way to maintain the Yocto project for
> an embedded product - git submodules or repo or using Combo-layer
> 
> On 18 January 2017 09:32:15 GMT+00:00, "Eswaran Vinothkumar (BEG-PT/PJ-
> IOT1)"  wrote:
> >Hello Yocto community members,
> >
> >Currently I am working on the task of using Yocto to build customized
> >Embedded Linux distribution for an embedded product. I have created a
> >new BSP layer for my project (meta-custommachine) and have successfully
> >created barebox, Linux Kernel and root filesystem images for my board.
> >
> >Now I wish to create an internal repository for Yocto project to track
> >and maintain the changes. I am unclear what is the better way to create
> >an repository. I googled for the same and found that the Freescale
> >community is maintaining their Yocto project using the repo tool. So I
> >tried to have a similar structure for my project. I created a repo with
> >the default.xml file which has the information about where to fetch the
> >repositories for poky, meta-ptx and meta-custommachine. I am seeing the
> >folder structures as expected and build is also fine.
> >
> >I had a discussion with one of my senior team member about this and he
> >is interested in using git submodules. So I tried to add the layers
> >meta-custommachine and meta-ptx within poky repository as sub-
> modules.
> >Is this the proper way of adding new layers within the poky repository?
> >Or may I know how can I maintain a Yocto repository using git
> >submodules. Does git submodules work better than repo tool ?
> >
> >I am newbie to create and maintain a repo, so I am not able to
> >visualize what is the future effect of choosing one over the other.
> >Currently I am using the krogoth release of Yocto and planning to
> >update this with new Yocto releases.
> >
> >Any information on the topic would be helpful.
> 
> Both of these approaches are widely used, I'd go with whichever feels most
> comfortable to you/your team. Personally I'm a fan of using repo as I can set
> it to check out the latest commits on a given branch (eg. krogoth) instead of
> always having to set an exact commit hash to use.
> 
> If using git submodules it is often advised to have a separate top level
> repository which just pulls in the submodules.

Alexander Kanevskiy (aka Sasha) touched on some of that especially in the 
context of delivering a Continuous Integration and Continuous Delivery 
mechanism in his presentation at the last ELCE in Berlin. You can view his 
slides here: 
http://events.linuxfoundation.org/sites/events/files/slides/Creating%20Continuous%20Delivery%20for%20Yocto%20Based%20IoT%20Distribution%2020161012%20LF.pdf

There is a quick summary of the pro's and con's of using combo-tool vs. git 
submodule on slide 20.

Geoffroy
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] which meta-intel woudl build a kernel 4.8

[VanCutsem, Geoffroy]

 Original message 
From: "Dominig ar Foll (Intel Open Source)" 
Date: 06/10/2016 20:16 (GMT+01:00)
To: yocto@yoctoproject.org
Subject: [yocto] which meta-intel woudl build a kernel 4.8

Hello,

I was happily under 'jethro' until now but I need to build a kernel 4.8
fir Intel HW to get access to some new features.

I can see that the 'master' branch bump to 4.8 but unfortunately come
with the following errors :

ERROR: No recipes available for:

/home/dominig/AGL/meta-intel/common/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend

/home/dominig/AGL/meta-intel/common/recipes-kernel/linux/linux-yocto_4.8.bbappend

Would someone have an idea how I could get a 4.8 working meta-intel ?

[Geoffroy] I don't know how the overall AGL repo is constructed but it sounds 
like you would need to update your openembedded-core as well to master to have 
the base recipes for 4.8 (in meta/recipes-kernel/linux)

Geoffroy

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto