Re: [yocto] inheriting native.bbclass explicitly

On Thu, Sep 13, 2018 at 6:05 AM, Dudziak Krzysztof wrote: > Current release's reference manual issues in native.bbclass chapter a warning: > "When creating a recipe, you must follow this naming convention: > native-myrecipe.bb > Not doing so can lead to subtle problems because code exists th

Re: [yocto] Whitelist gdbserver

On Thu, Sep 13, 2018 at 8:42 AM, Jeremy Overesch wrote: > HI all, > > I’m attempting to whitelist gdbserver just for SDK purposes, while keeping > all other GPLv3 code as incompatible (therefore unbuilt). However, > everything I’ve tried still results in gdbserver being removed from my SDK > and

Re: [yocto] inheriting native.bbclass explicitly

Current release's reference manual issues in native.bbclass chapter a warning: "When creating a recipe, you must follow this naming convention: native-myrecipe.bb Not doing so can lead to subtle problems because code exists that depends on the naming convention." Jethro release manual does

Re: [yocto] inheriting native.bbclass explicitly

Thanks for hints. I don't want to have this package on target system. You sound like inheriting explicitly had some major drawback of wide scope. I am familiarized with bitbake -e I know it as a way to print package/image tasks variables. But how its output shows the list of classes inherited

Re: [yocto] bitbake error

Sometimes, I also got some weird errors like that when copying and pasting projects (or meta layers) from one machine to other. That's because the flags and some file stats are not copied. On Thu, 13 Sep 2018, 18:57 Alexander Kanavin, wrote: > It seems as though the build system is unable to cre

Re: [yocto] inheriting native.bbclass explicitly

Got it and will follow your recommendation. Thanks. -Original Message- From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, 13. September 2018 14:00 To: Dudziak Krzysztof Cc: yocto@yoctoproject.org Subject: Re: [yocto] inheriting native.bbclass explicitly On 13 September 201

Re: [yocto] bitbake error

It seems as though the build system is unable to create this directory: /home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8 You probably have a permission problem there, working from /home/b but attempting to create /home/yocto.

Re: [yocto] Notes: Yocto Project Weekly Triage Meeting

On 09/13/2018 11:17 AM, Jolley, Stephen K wrote: Attendees: Stephen, Armin, Joshua, Amanda, Richard, Ross, Randy, Anuj, Wiki: _https://wiki.yoctoproject.org/wiki/Bug_Triage_ AR: Ross - Update _12921_ to NEEDINFO and add comment. AR: Arm

[yocto] Whitelist gdbserver

HI all, I'm attempting to whitelist gdbserver just for SDK purposes, while keeping all other GPLv3 code as incompatible (therefore unbuilt). However, everything I've tried still results in gdbserver being removed from my SDK and therefore failing to build. In my local.conf, I have the followi

[yocto] Notes: Yocto Project Weekly Triage Meeting

Attendees: Stephen, Armin, Joshua, Amanda, Richard, Ross, Randy, Anuj, Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage AR: Ross - Update 12921 to NEEDINFO and add comment. AR: Armin – Create selftest bug for 12921

[yocto] Building, Using SDK

Hi, Alex González elaborates in his book Embedded Linux Development Using Yocto Projets (2nd Edition) SDK-related questions - basics, building, usage (chapter 4). 1. Downloading then installing precompiled SDK was one of all available options according to Alex. He elaborates how to find it on s

Re: [yocto] [meta-rockchip] conf: machine: Add support for vyasa-rk3288

> Hello Shyam, Hi Trevor > Thank you for your contribution! > > I just have 3 small nits with your patch, which I am happy to fix myself > without you needing to send a v2 (if that's okay with you): I'm perfectly fine with it. You can merge them it with your fixes. > 1. I see that there's a mis

[yocto] bitbake error

Hi, i'm trying to build an image with Yocto on a new machine (ubuntu 16.04 LTS)but i have this error that i can't resolve. Can you help ? ERROR: Execution of event handler 'uninative_event_fetchloader' failed Traceback (most recent call last): File "/home/b/yocto-krogoth/sources/poky/meta/c

Re: [yocto] inheriting native.bbclass explicitly

On 13 September 2018 at 12:39, Dudziak Krzysztof wrote: > Thanks for hints. > I don't want to have this package on target system. > You sound like inheriting explicitly had some major drawback of wide scope. It won't be included in the image unless you add it to the image. Ross -- _

Re: [yocto] inheriting native.bbclass explicitly

CCing the list again. Please remember to reply to the list. On 13 September 2018 at 11:42, Dudziak Krzysztof wrote: > Is it possible for one Bitbake target to check list and order of classes > inherited? bitbake -e [recipe] will show you what was parsed. In this situation I wouldn't worry too

[yocto] inheriting native.bbclass explicitly -- more details

autconf-archive's recipe as for OE-core layer builts also native package in BBCLASSEXTEND-based fashion. I like for system built here to change the approach to explicit-class-inheritance fashion in .bbappend in own layer. Will it suffice to ensure native.bbclass is explicitly inherited as last cla

Re: [yocto] inheriting native.bbclass explicitly

Adding yocto@ back to CC. Please remember to mail the list and not the sender. On 13 September 2018 at 10:34, Dudziak Krzysztof wrote: > Will BBCLASSEXTEND=native fashion also build target system package? > This is what is not needed (autoconf-archive on target system). > Therefore thoughts turn

[yocto] ext4 rootfs in wrong folder when trying to build sdcard image

This is for a custom carrier board using the Phytec rk3288 SOM. This worked for 2.2 morty. I have migrated to 2.5 sumo. I am using their rk3288_sd_image-phy.bbclass file. This file is only in the morty branch so I had to copy it into my bsp layer. I am still a bit of a Yocto noob so any help wou

Re: [yocto] inheriting native.bbclass explicitly

On 13 September 2018 at 10:17, Dudziak Krzysztof wrote: > Is this rule’s scope literally each single recipe separately > > or rather the compound .bb file + set of matching .bbappends? Compound. > I am going to use that method for building autoconf-archive package > > as for device built here th

Re: [yocto] allarch class used in autoconf-archive recipe

Re-adding yocto@ to CC. On 13 September 2018 at 09:42, Dudziak Krzysztof wrote: > Myself does not address level of warnings. TBH I did not check how the > warnings status is. > Myself operates currently at recipe's level, no more. > In lights of my understanding, which of course might still be w

[yocto] inheriting native.bbclass explicitly

Hi, YP reference manual chapter 6.83 "native.bbclass" https://www.yoctoproject.org/docs/2.5.1/ref-manual/ref-manual.html#ref-classes-native reads: "*Create a myrecipe-native.bb that inherits the native class. If you use this method, you must order the inherit statement in the recipe after all oth

[yocto] [PATCH yocto-docs] ref-manual: Introduce the --use-label partition parameter for wic

Signed-off-by: Kevin Hao --- documentation/ref-manual/ref-kickstart.xml | 10 ++ 1 file changed, 10 insertions(+) diff --git a/documentation/ref-manual/ref-kickstart.xml b/documentation/ref-manual/ref-kickstart.xml index a58f9d7c9602..dd97dd7206c7 100644 --- a/documentation/ref-manual/r