Re: [yocto] Prescribed way to make global variables in recipes?

On Fri, Apr 8, 2016 at 10:22 AM, Andy Gikling wrote: > This doesn’t seem to be a viable option. I’m still missing something I > think. > > We are adding our own layer on top of our soc vendor’s layer. In their > layer there is a specialized u-boot recipe for the imx6 we are using. > > So I try t

Re: [yocto] Prescribed way to make global variables in recipes?

This doesn’t seem to be a viable option. I’m still missing something I think. We are adding our own layer on top of our soc vendor’s layer. In their layer there is a specialized u-boot recipe for the imx6 we are using. So I try to make a recipe for uboot (u-boot-faux_2014.04.bb

[yocto] Yocto Project Status WW15

Current Dev Position: YP 2.1 M4 (Stabilization only milestone.) Next Deadline: YP 2.1 Final Release Target: April 29, 2016 SWAT team rotation: Saul -> Paul https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: *YP 2.1 M3.rc2 was released *YP 2.

Re: [yocto] Prescribed way to make global variables in recipes?

On 8 April 2016 at 16:05, Andy Gikling wrote: > So what do I do in that case? Just make two of my own versions of the > u-boot_2014.04.bb file, and give them different names? For example “ > u-boot-faux_2014.04.bb” and “u-boot-faux-debug_2014.04.bb” ? That should > work but does that make sense

Re: [yocto] Prescribed way to make global variables in recipes?

Ross, Perfect thank you so much. That makes total sense now. I like the idea of just having two different recipes and then use IMAGE_INSTALL. However, in the u-boot example I’m actually just using a bbappend to the u-boot recipe provided with our target SOM’s bsp. Can I select different bba

Re: [yocto] Prescribed way to make global variables in recipes?

On 8 April 2016 at 15:30, Andy Gikling wrote: > Dear Yocto, > > > > First of all, I love this project. Thanks for all your hard work. > > > > Question: What is the prescribed way to allow image recipes to make > global configuration variables that other recipes can use? > > You can't. The basi

[yocto] Prescribed way to make global variables in recipes?

Dear Yocto, First of all, I love this project. Thanks for all your hard work. Question: What is the prescribed way to allow image recipes to make global configuration variables that other recipes can use? After extensive research and educating myself on how bitbake works, it seems that what

Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2

On 04/07/2016 07:58 PM, Chris Trobridge wrote: http://cgit.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python > > Will be fixed by deprecating python 2, of course. > > Alex Is there a shorter term solution that's generally applicable, like a separate python3-gobjec

[yocto] does any YP guide show clearly how to use a local git kernel repo?

in my travels, i frequently read online about people asking how to set up a kernel recipe to point at a local kernel source tree or local kernel git repo and, as best i can tell, this isn't really explained in any kind of detail in any YP guide, including the kernel development guide. it seem

Re: [yocto] [meta-selinux][PATCH 2/3] Integrate selinux-config into refpolicy_common.

This causes do_populate_sysroot error if build two or more types of refpolicy: $ bitbake refpolicy-minimum && bitbake refpolicy-mls ERROR: refpolicy-mls-git-r0 do_populate_sysroot: The recipe refpolicy-mls is trying to install files into a shared area when those files already exist. Those fil

[yocto] [PATCH][meta-selinux] refpolicy-minimum: port changes for prepare_policy_store

From: Wenzong Fan Apply the changes to refpolicy-minimum_2.20151208.bb: commit bfaf278116e6c3a04bb82c9f8a4f8629a0a85df8 Author: Wenzong Fan Date: Tue Oct 27 06:25:04 2015 -0400 refpolicy-minimum: update prepare_policy_store * update prepare_policy_store() for supporting SELinu