Re: [yocto] Removing busybox completely from the generated image

[Martin Hundebøll]

Hi Ivan,

On 2018-02-19 17:13, Iván Castell wrote:



2018-02-19 16:18 GMT+01:00 Maxin B. John >:


Hi,

On Mon, Feb 19, 2018 at 02:17:38AM -0800, Khem Raj wrote:
> On Mon, Feb 19, 2018 at 12:35 AM, Iván Castell
> mailto:icast...@nayarsystems.com>> wrote:
> > I have tried breaking apart packagegroup-core-boot, making a copy in my
> > custom layer, removing the line referencing busybox:
> >
> >     ## VIRTUAL-RUNTIME_login_manager ?= "busybox"

Have you considered "toybox" ? It probably wouldn't work right-away.
Still,
toybox was designed to provide a replacement for busybox. It is
available
in "meta-oe"


http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-core/toybox/toybox_0.7.5.bb





Thank you for the information, I will take into account that tool for 
future embedded projects. However, the focus of this issue was to remove 
completely busybox from the image, not replacing it by another 
application box.


I have created a bbappend with a fragment of the busybox configuration 
disabling syslog and udhcpc applets. It works. However the busybox 
binary and a lot of applets are still there (adduser, unzip, fbset, 
traceroute, and more).


Disabling all different applets and installing native tools instead 
could be the right way to procede. Not a nice solution, but at least it 
should work...


Here's what we have in our distro config to disable busybox:

> # Disable busybox
> VIRTUAL-RUNTIME_base-utils = ""
> ALTERNATIVE_PRIORITY_pn-busybox = "1"

The priority setting make bitbake pull in alternatives from util-linux / 
coreutils when appropriate.


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

Re: [yocto] Removing busybox completely from the generated image

[Iván Castell]

2018-02-20 7:45 GMT+01:00 Martin Hundebøll :

> Hi Ivan,
>
>>
>> Thank you for the information, I will take into account that tool for
>> future embedded projects. However, the focus of this issue was to remove
>> completely busybox from the image, not replacing it by another application
>> box.
>>
>> I have created a bbappend with a fragment of the busybox configuration
>> disabling syslog and udhcpc applets. It works. However the busybox binary
>> and a lot of applets are still there (adduser, unzip, fbset, traceroute,
>> and more).
>>
>> Disabling all different applets and installing native tools instead could
>> be the right way to procede. Not a nice solution, but at least it should
>> work...
>>
>
> Here's what we have in our distro config to disable busybox:
>
> > # Disable busybox
> > VIRTUAL-RUNTIME_base-utils = ""
> > ALTERNATIVE_PRIORITY_pn-busybox = "1"
>
> The priority setting make bitbake pull in alternatives from util-linux /
> coreutils when appropriate.
>
> // Martin
>


Yes!! That was the trick. It works like a charm!! Thank you so much Mr.
Martin!! :-)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-qt5] UnicodeDecodeError suddenly appeared

[Iain Worlock]

Bit of a strange one here, this exact configuration used to build just fine, 
but now fails. I have no custom bbappends in my qt5 layers, so it should really 
just be a vanilla build from meta-qt5.

Failure looks like this:

$ bitbake meta-toolchain-qt5
NOTE: Started PRServer with DBfile: 
/media/parallels/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 38360, PID: 
18679
Loading cache: 100% 
|###|
 ETA:  00:00:00
Loaded 2898 entries from dependency cache.
Parsing recipes: 100% 
|#|
 Time: 00:00:01
Parsing of 2362 .bb files complete (2359 cached, 3 parsed). 2900 targets, 156 
skipped, 9 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.26.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "overo"
DISTRO= "poky"
DISTRO_VERSION= "1.8"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "(nobranch):83aa565d93aacae484976562ef1ae8dbbb6b2bc0"
meta-gnome
meta-oe
meta-xfce
meta-systemd
meta-networking
meta-multimedia
meta-python   = "(nobranch):10d3c8f85280a0bf867a8e4f84bcda81c290d28e"
meta-gumstix  = "(nobranch):68e4b5771aef2d11fcf04bb8759fecd409de1ac3"
meta-gumstix-extras = "(nobranch):0ee78d47ff3082000e9e087b1ec0d56df13457d9"
meta-bluechiip= "HHR-STREAM4:a60b5fb37479e2ff1348ab100c0f3735713a730c"
meta-ros  = "(nobranch):d465a23c0a96e651419d46b29ab7c0c3663da314"
meta-ti   = "(nobranch):03cb3ff15f3b8535ca409ce682f44ec1b81da0c3"
meta-java = "(nobranch):66c97ae7461f4c1a13917131787bb76dc34e6b6f"
meta-qt5  = "(nobranch):90919b9d86988e7da01fa2c0a07246b5b5600a5d"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Unable to install packages. Command 
'/media/parallels/build/tmp/sysroots/x86_64-linux/usr/bin/smart --quiet 
--data-dir=/media/parallels/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/sdk/image/opt/poky/1.8/sysroots/cortexa8hf-vfp-neon-poky-linux-gnueabi/var/lib/smart
 install -y packagegroup-core-standalone-sdk-target-dbg@all 
packagegroup-core-standalone-sdk-target@all 
packagegroup-qt5-toolchain-target@all' returned 1:
Traceback (most recent call last):
  File 
"/media/parallels/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/smart/backends/rpm/pm.py",
 line 358, in __call__
self._process_rpmout()
  File 
"/media/parallels/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/smart/backends/rpm/pm.py",
 line 343, in _process_rpmout
output = self.rpmout.read()
  File 
"/media/parallels/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/codecs.py", 
line 474, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4948: 
ordinal not in range(128)

ERROR: Function failed: do_populate_sdk
ERROR: Logfile of failure stored in: 
/media/parallels/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/temp/log.do_populate_sdk.18850
ERROR: Task 7 
(/home/parallels/yocto/poky/meta-qt5/recipes-qt/meta/meta-toolchain-qt5.bb, 
do_populate_sdk) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4705 tasks of which 4704 didn't need to be rerun 
and 1 failed.
No currently running tasks (4704 of 4706)


(A bit more verbosity on the exact point of failure...)

$ bitbake -v -c populate_sdk meta-toolchain-qt5

NOTE: Executing 
'/media/parallels/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo --dbpath 
/media/parallels/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/rpmdb/cortexa8hf_vfp_neon
 --update -q /media/parallels/build/tmp/deploy/rpm/cortexa8hf_vfp_neon' ...
NOTE: Executing 
'/media/parallels/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo --dbpath 
/media/parallels/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/rpmdb/x86_64_nativesdk
 --update -q /media/parallels/build/tmp/deploy/rpm/x86_64_nativesdk' ...
NOTE: Installing the following packages: 
packagegroup-core-standalone-sdk-target-dbg 
packagegroup-core-standalone-sdk-target packagegroup-qt5-toolchain-target
NOTE: to be installed: packagegroup-core-standalone-sdk-target-dbg@all 
packagegroup-core-standalone-sdk-target@all 
packagegroup-qt5-toolchain-target@all
NOTE: /media/parallels/build/tmp/sysroots/x86_64-linux/usr/bin/smart --quiet 
--data-dir=/media/parallels/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/sdk/image/opt/poky/1.8/sysroots/cortexa8hf-vfp-neon-poky-linux-gnueabi/

Re: [yocto] Yocto Recipe for LibRXE.

[Vish (Vishwanath) Maram]

Ross,

Can you point me to what devtool you are talking about to generate the recipe? 
I am in process of learning tools on FPGA, not sure on how to generate as well?

-Vish

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, February 15, 2018 2:55 AM
To: Vish (Vishwanath) Maram 
Cc: meta-virtualizat...@yoctoproject.org; yocto@yoctoproject.org
Subject: Re: [yocto] Yocto Recipe for LibRXE.

It's not in the layer index 
(http://layers.openembedded.org/layerindex/branch/master/recipes/?q=librxe), so 
I suggest you start with devtool to create a new recipe.

Ross

On 7 February 2018 at 17:43, Vish (Vishwanath) Maram 
mailto:vishwanat...@samsung.com>> wrote:
Hi,

I am looking for a yocto recipe of librxe? Right now I was able to get 
librdmacm and libibverbs, but librxe yocto is not there. Can someone help me in 
getting this?

Highly appreciate if I can get some info on the same.

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

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

[yocto] [YOCTO] add a new partition during flash with mfgtools

[Thibaut SARRAZIN]

Hello everybody,


I don't find solution to add a new partition to my emmc directly during 
the flash. I don't know if I need to modify the u-boot-fslc recipe or if 
there is another solution.


board : mx6qroj


Thanks you all  for your help,

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

Re: [yocto] Splashscreen using psplash

[Tian Wen See]

Hello,

How do i modify the original psplash in Yocto, and how do i recompile it and 
reintegrate the newly compiled one into Yocto ?
Any help will be greatly appreciated.

Best Regards,
Mike See

Sent from Mail for Windows 10

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

[yocto] Yocto Project Status WW08’18

[Jordan, Robin L]

Current Dev Position: YP 2.5 M3 development

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 is imminent! ***


SWAT team rotation: Tracy -> Stephano on Feb. 16, 2018.

SWAT team rotation: Stephano -> Maxin John on Feb. 23, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   YP 2.5 M2 is 97% through QA. See: 
https://wiki.yoctoproject.org/wiki/2.5_QA_Status
  *   YP 2.2.3 is also mostly through QA. See 
https://wiki.yoctoproject.org/wiki/2.2_QA_Status
  *   We build 2.4.2 rc1 however rapidly moving kernel updates combined with QA 
not having started on rc1 yet meant we decided to build rc2, pulling in further 
kernel security fixes (as well as others like openssl). rc2 is currently being 
built and should enter QA today assuming a successful build.
  *   autobuilder.yoctoproject.org continues to be unavailable as we continue 
to develop the new autobuilder codebase to replace the current heavily 
customized buildbot one.
  *   We managed to shrink the ltp package size which unblocked some patch 
merging. Bruce has been working on changes to kernel-devsrc to significantly 
reduce its size.
  *   The glibc change continues to be blocked on locale issues which may prove 
tricky to resolve and will block M3 as we need the glibc upgrade for various 
reasons.
  *   We have some key decisions to make about the conflicting native of 
pkg-conf and pkgconfig. Maxin has a patch series which exposes the issues.
  *   There are problems with the changes to pseudo’s master branch verses the 
patches we have against the recipe.
  *   Please note that we are very close to M3 which is feature freeze, 
technically, feature freeze was yesterday. We’re not in a position to build M3 
yet but if there are features you expect to see in 2.5, please highlight those 
patches ASAP. We are drawing up a list of “must haves” for the release and if 
we don’t know about it, it likely won’t be on it.


Planned upcoming dot releases:

YP 2.4.2 (Rocko) is currently being built and should enter QA today.

YP 2.3.4 (Pyro) will be built when we figure out gcc backports.

YP 2.2.3 (Morty) rc2 is in QA.

YP 2.2.4 (Morty) will be built when we figure out gcc backports.


Key YP 2.5 Dates are:

YP 2.5 M2 cut off is past, it is in QA.

YP 2.5 M2 release of 1/26/18

YP 2.5 M3 cut off of 2/19/18

YP 2.5 M3 release of 3/2/18

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

WDD 2648 (last week  2610)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

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

[yocto] Yocto Project Status WW08’18

[Jolley, Stephen K]

Current Dev Position: YP 2.5 M3 development

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 is imminent! ***


SWAT team rotation: Tracy -> Stephano on Feb. 16, 2018.

SWAT team rotation: Stephano -> Maxin John on Feb. 23, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   YP 2.5 M2 is 97% through QA. See: 
https://wiki.yoctoproject.org/wiki/2.5_QA_Status
  *   YP 2.2.3 is also mostly through QA. See 
https://wiki.yoctoproject.org/wiki/2.2_QA_Status
  *   We build 2.4.2 rc1 however rapidly moving kernel updates combined with QA 
not having started on rc1 yet meant we decided to build rc2, pulling in further 
kernel security fixes (as well as others like openssl). rc2 is currently being 
built and should enter QA today assuming a successful build.
  *   autobuilder.yoctoproject.org continues to be unavailable as we continue 
to develop the new autobuilder codebase to replace the current heavily 
customized buildbot one.
  *   We managed to shrink the ltp package size which unblocked some patch 
merging. Bruce has been working on changes to kernel-devsrc to significantly 
reduce its size.
  *   The glibc change continues to be blocked on locale issues which may prove 
tricky to resolve and will block M3 as we need the glibc upgrade for various 
reasons.
  *   We have some key decisions to make about the conflicting native of 
pkg-conf and pkgconfig. Maxin has a patch series which exposes the issues.
  *   There are problems with the changes to pseudo’s master branch verses the 
patches we have against the recipe.
  *   Please note that we are very close to M3 which is feature freeze, 
technically, feature freeze was yesterday. We’re not in a position to build M3 
yet but if there are features you expect to see in 2.5, please highlight those 
patches ASAP. We are drawing up a list of “must haves” for the release and if 
we don’t know about it, it likely won’t be on it.


Planned upcoming dot releases:

YP 2.4.2 (Rocko) is currently being built and should enter QA today.

YP 2.3.4 (Pyro) will be built when we figure out gcc backports.

YP 2.2.3 (Morty) rc2 is in QA.

YP 2.2.4 (Morty) will be built when we figure out gcc backports.


Key YP 2.5 Dates are:

YP 2.5 M2 cut off is past, it is in QA.

YP 2.5 M2 release of 1/26/18

YP 2.5 M3 cut off of 2/19/18

YP 2.5 M3 release of 3/2/18

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

WDD 2648 (last week  2610)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Release Engineer
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•   Work Telephone:   (503) 712-0534
•Cell:(208) 244-4460
• Email: stephen.k.jol...@intel.com

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

Re: [yocto] Small documentation issue

[Anuj Mittal]

On 02/20/2018 02:33 PM, Zoran Stojsavljevic wrote:
> Hello,
> 
> Just to point to the documentation issue on YOCTO Projects wiki page:
> https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_change_the_root_password
> 
> This line:
> inherit extrausers
> 
> Should be changed as:
> INHERIT += "extrausers"

This shows how to do it from a recipe. For a more up-to-date documentation:

https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-classes-extrausers

INHERIT is used in a configuration file.

http://www.yoctoproject.org/docs/2.5/bitbake-user-manual/bitbake-user-manual.html#inherit-configuration-directive

"inherit" on the other hand is used in a recipe or class.

http://www.yoctoproject.org/docs/2.5/bitbake-user-manual/bitbake-user-manual.html#inherit-directive

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

Re: [yocto] Small documentation issue

[Paul Eggleton]

Hi Zoran,

On Tuesday, 20 February 2018 7:33:22 PM NZDT Zoran Stojsavljevic wrote:
> Just to point to the documentation issue on YOCTO Projects wiki page:
> https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_change_the_root_password
> 
> This line:
> inherit extrausers
> 
> Should be changed as:
> INHERIT += "extrausers"
> 
> To be inline with bitbake syntax. It is somehow confusing.

I've now fixed the page - basically that only applies if you are setting it
in your configuration, the example was for an image recipe (although it
did not state as such, it does now).

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


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

Re: [yocto] Removing busybox completely from the generated image

[Paul Eggleton]

On Tuesday, 20 February 2018 9:26:49 PM NZDT Iván Castell wrote:
> 2018-02-20 7:45 GMT+01:00 Martin Hundebøll :
> >> Thank you for the information, I will take into account that tool for
> >> future embedded projects. However, the focus of this issue was to remove
> >> completely busybox from the image, not replacing it by another
> >> application box.
> >>
> >> I have created a bbappend with a fragment of the busybox configuration
> >> disabling syslog and udhcpc applets. It works. However the busybox binary
> >> and a lot of applets are still there (adduser, unzip, fbset, traceroute,
> >> and more).
> >>
> >> Disabling all different applets and installing native tools instead could
> >> be the right way to procede. Not a nice solution, but at least it should
> >> work...
> >>
> >
> > Here's what we have in our distro config to disable busybox:
> >
> > > # Disable busybox
> > > VIRTUAL-RUNTIME_base-utils = ""
> > > ALTERNATIVE_PRIORITY_pn-busybox = "1"
> >
> > The priority setting make bitbake pull in alternatives from util-linux /
> > coreutils when appropriate.
> 
> Yes!! That was the trick. It works like a charm!! Thank you so much Mr.
> Martin!! :-)

I will note that the priority currently set in busybox.inc is 50, which is 
lower than coreutils 100 (or 90 for hostname), so that part shouldn't be 
needed for coreutils. There are one or two other recipes that set a priority 
lower than 50 for reasons that are not immediately clear to me. 

Additionally, ALTERNATIVE_PRIORITY won't do anything to control what goes into 
the image - it only controls which binary is selected at runtime when more 
than one providing the same binary is installed. Thus I can only assume that 
it was the VIRTUAL-RUNTIME_base-utils = "" that finally removed the packages 
you wished removed.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


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

Re: [yocto] Small documentation issue

[Zoran Stojsavljevic]

Hello Paul,

> If you prefer to do this in local.conf or your distro configuration,
you'll need to change the first line to INHERIT += "extrausers".

I see. Makes it very clear.

Thank you,
Zoran
___

On Wed, Feb 21, 2018 at 3:51 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:

> Hi Zoran,
>
> On Tuesday, 20 February 2018 7:33:22 PM NZDT Zoran Stojsavljevic wrote:
> > Just to point to the documentation issue on YOCTO Projects wiki page:
> > https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_
> change_the_root_password
> >
> > This line:
> > inherit extrausers
> >
> > Should be changed as:
> > INHERIT += "extrausers"
> >
> > To be inline with bitbake syntax. It is somehow confusing.
>
> I've now fixed the page - basically that only applies if you are setting it
> in your configuration, the example was for an image recipe (although it
> did not state as such, it does now).
>
> Thanks,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Small documentation issue

[Zoran Stojsavljevic]

Sorry, Anuj, I did not reply to you in the same email. :-(

I'll look into the pointers you have sent to me, but over the weekend (I am
very busy over the week).

Thank you,
Zoran
___

On Wed, Feb 21, 2018 at 3:09 AM, Anuj Mittal  wrote:

> On 02/20/2018 02:33 PM, Zoran Stojsavljevic wrote:
> > Hello,
> >
> > Just to point to the documentation issue on YOCTO Projects wiki page:
> > https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_
> change_the_root_password
> >
> > This line:
> > inherit extrausers
> >
> > Should be changed as:
> > INHERIT += "extrausers"
>
> This shows how to do it from a recipe. For a more up-to-date documentation:
>
> https://www.yoctoproject.org/docs/latest/ref-manual/ref-
> manual.html#ref-classes-extrausers
>
> INHERIT is used in a configuration file.
>
> http://www.yoctoproject.org/docs/2.5/bitbake-user-manual/
> bitbake-user-manual.html#inherit-configuration-directive
>
> "inherit" on the other hand is used in a recipe or class.
>
> http://www.yoctoproject.org/docs/2.5/bitbake-user-manual/
> bitbake-user-manual.html#inherit-directive
>
> Thanks,
> Anuj
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto