[yocto] openssl does not support building for SDK_MACHINE x86_64-mingw32

Hi all, Since December, glib is pulling python3 for codegen, which because of BBCLASSEXTENDS, tries to build nativesdk-python3 which in turn tries to build nativesdk-openssl, and it looks like openssl does not support it SDK_MACHINE=x86_64-mingw32 There is a do_configure error and I get

Re: [yocto] Adding GCC to system root image

On Thu, Jun 21, 2018 at 4:02 PM Krishna Priya wrote: > > Hello all, > > I am trying to add gcc to the system image by modifying the following files. > poky/meta-qti-bsp/recipies-products/images/ BASE_IMAGE.inc > > + IMAGE_INSTALL +="opkg" > + IMAGE_INSTALL +="packagegroup-core-buildessential" > >

[yocto] Adding GCC to system root image

Hello all, I am trying to add gcc to the system image by modifying the following files. poky/meta-qti-bsp/recipies-products/images/ BASE_IMAGE.inc + IMAGE_INSTALL +="opkg" + IMAGE_INSTALL +="packagegroup-core-buildessential" poky/build/conf/local.conf + EXTRA_IMAGE_FEATURES = "tools-sdk

Re: [yocto] porting gRPC into Yocto

>From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] >On Behalf Of Simon Chamlian >Sent: 21 June 2018 19:50 >To: Rudolf J Streif >Cc: yocto@yoctoproject.org >Subject: Re: [yocto] porting gRPC into Yocto > >Thank you everyone for such a prompt response. > >What do I do

Re: [yocto] porting gRPC into Yocto

Thank you everyone for such a prompt response. What do I do with the grpc_1.8.5.bb recipe file (sorry for my ignorance, it has been 1 day I am using Yocto)? Simon On Thu, Jun

Re: [yocto] porting gRPC into Yocto

Hi Simon, Thank you for using the Yocto Project and reaching out. For any open-source component that you would like to add to the Yocto Project I recommend that you first have a look at http://layers.openembedded.org/layerindex/branch/master/recipes/ and enter the name of the component. Chances

Re: [yocto] porting gRPC into Yocto

There's a grpc recipe in meta-oe: http://layers.openembedded.org/layerindex/recipe/72419/ Ross On 21 June 2018 at 19:15, Simon Chamlian wrote: > Hi, > > I just started using Yocto. > > Is there a detailed procedure on how I can port gRPC (for C or C++) into a > Yocto project? > > Thanks, > > S

Re: [yocto] porting gRPC into Yocto

Hi, I just started using Yocto. Is there a detailed procedure on how I can port gRPC (for C or C++) into a Yocto project? Thanks, S -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-cloud-services] spice: remove spice receipe from meta-cloud-services

On 06/21/2018 02:11 AM, Changqing Li wrote: spice have been export to meta-openembedded/meta-networking, and have newer version. spice under this layer now have compile error, but spice under networking layer don't. Maybe we should not maintain 2 same spices, so delete it. I'm going to hold

[yocto] Basehash value changed issue

Hi, I am facing issue with basehash value changed while building image on one of my test board (Ref of beagle bone) on morty branch. Error : gateway.bb.do_rootfs, the basehash value changed from e685a429b8df6dcff60063f087d425ee to 3f98a102f48ea8722835ad0d65bfbc1f. The metadata is not

[linux-yocto] [PATCH] kernel features about debug: gather debug features

Collect debug configs and classify them into functional subdirectories. Signed-off-by: Hongzhi.Song --- cfg/debug/README | 0 cfg/debug/common/debug-kernelhacking.cfg | 1 + cfg/debug/common/debug-kernelhacking.scc | 1 +

[linux-yocto] [yocto-4.14][PATCH] cfg/debug: add debug directory to debug or test kernel

Look throuth all kernel fragments and sort debug/test fragments out into individual functional subdirectory. Each fragment is standalone as far as possible. --Hongzhi Hongzhi.Song (1): kernel features about debug: gather debug features cfg/debug/README | 0

[yocto] [PATCH][meta-cloud-services] spice: remove spice receipe from meta-cloud-services

spice have been export to meta-openembedded/meta-networking, and have newer version. spice under this layer now have compile error, but spice under networking layer don't. Maybe we should not maintain 2 same spices, so delete it. Signed-off-by: Changqing Li ---