Re: [yocto] Concept clarification: can we deploy Yocto SDK to target?

Hi Jerry, On Thursday, 30 November 2017 10:35:32 AM NZDT Jerry Lian wrote: > I am confused about the concept of Yocto SDK: > * when we use "bitbake -c populate_sdk some_image", we obtain sysroots for > both target and host. > * But why do we need sysroot for host? The host sysroot actually

[yocto] BKM for Importing Python Modules

I have a python function that I've added to PACKAGEFUNCS in a bbclass, and I want to use python-cryptography in that function. However, sys.path doesn't seem setup to allow this import. I'm curious to know the best known method for using python modules that are outside of /lib directory.

Re: [yocto] buildhistory.bbclass "version-going-backwards" for AUTOINC

I think you can disable version-going-backwards check as any other QA check by removing it from WARN_QA and ERROR_QA variables. Even with AUTOINC you should use PR service to get increasing AUTOINC numbers, so the warning is correct, if you want working upgrade paths on the device then you need

[yocto] [meta-raspberrypi][PATCH] rpi-config: Setup lcd_rotate for Raspberry Pi display

From: Drew Moseley Signed-off-by: Drew Moseley --- docs/extra-build-config.md | 6 ++ recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++ 2 files changed, 12 insertions(+) diff --git a/docs/extra-build-config.md

[yocto] [PATCH] dev-manual: Fix DEFAULTTUNE link

Signed-off-by: Joshua Watt --- documentation/dev-manual/dev-manual-common-tasks.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index

[yocto] Concept clarification: can we deploy Yocto SDK to target?

I am confused about the concept of Yocto SDK: * when we use "bitbake -c populate_sdk some_image", we obtain sysroots for both target and host. * But why do we need sysroot for host? * I know we can build application under target-sysroot (surely source the environment), with fast speed. * But can

[yocto] buildhistory.bbclass "version-going-backwards" for AUTOINC

I am getting these errors during builds. clear-app-gitAUTOINC+4d250a7fe4-r0 do_packagedata: QA Issue: Package version for package clear-app-locale-es went backwards which would break pack age feeds from (0:git0+66636e50ea-r0 to 0:git0+4d250a7fe4-r0) [version-going-backwards] I think

Re: [linux-yocto] Custom wic imager plugin

What is the status of this patch? On Wed, Nov 22, 2017 at 3:28 AM, Ed Bartosh wrote: > Hi Paul, > > Thank you for the patch! > > +1 > > On Wed, Nov 15, 2017 at 04:56:16PM -0500, Paul Knopf wrote: > > Here is a patch for the master branch. It would be great it this

[yocto] Security upgrade stategy

Hello, I have an older yocto-based image built with Danny. We have a need to update two components, php and dropbear, to the most modern versions for security purposes. What is the preferred way to do this without moving the whole image to the latest version of poky/yocto? That would be a

Re: [yocto] Security upgrade stategy

On Wed, Nov 29, 2017 at 11:06 AM, Brian Smucker wrote: > Hello, > > I have an older yocto-based image built with Danny. > > We have a need to update two components, php and dropbear, to the most > modern versions for security purposes. > > What is the preferred way to do

Re: [yocto] Invalidating tasks

On 11/29/2017 11:10 AM, Alexander Kanavin wrote: > That would be a gross hack that goes against bitbake philosophy - > which is that once a task completes successfully, you never need to > re-run it again, unless the task content (or its dependencies) changes. > > What are you doing in do_A and

Re: [yocto] How to add support for "usb WIFI dongle"?

How can we tell whether "ipw2x00" is driver or firmware? * I check wiki: https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers * It seems that "ipw2x00" IS a driver, right? * (And logically, we should not be required to select firmware, right?) * (I mean: logically, if we

Re: [yocto] Invalidating tasks

On 11/29/2017 11:29 AM, Anton Gerasimov wrote: I've got two tasks, `do_A` and `do_B` (they are really IMAGE_CMDs if it's important). Now I want to introduce a third task, `do_check_A_and_B`, that will test that `do_A` and `do_B` have produced a correct result. If the test fails, I want to

[yocto] Invalidating tasks

Hi all, I've got two tasks, `do_A` and `do_B` (they are really IMAGE_CMDs if it's important). Now I want to introduce a third task, `do_check_A_and_B`, that will test that `do_A` and `do_B` have produced a correct result. If the test fails, I want to invalidate results of A and B, so that they