Re: [yocto] [OE-core] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Alexander Kanavin
On 11/17/2017 01:21 AM, Leonardo Sandoval wrote: isn't it this class meta/classes/insane.bbclass for this type of checks? This was already discussed - the test should be on the image rather than package level: http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144335.html

Re: [yocto] Trying to filter out 2 strings from EXTRA_OECONF, why doesn't this work?

2017-11-16 Thread Alexander Kanavin
On 11/17/2017 12:37 AM, Matt Schepers wrote: What do I have to do to filter out BOTH configure flags. I realize I can just write a new recipe, but I don't think that's the "correct" answer. The best way to fix this is to modify the original recipe so that all three options become PACKAGE

Re: [yocto] tiny-linux distribution with raspberrypi error

2017-11-16 Thread Zoran Stojsavljevic
> DISTRO = "poky-tiny" and i get the following What is the difference between core-image-minimal and poky-tiny? Thank you, Zoran On Fri, Nov 17, 2017 at 2:05 AM, Sherif Omran wrote: > hi > > i am trying to compile the yocto-tiny for raspberry pi by adding the > distro to my local.conf > > DI

[yocto] Trying to filter out 2 strings from EXTRA_OECONF, why doesn't this work?

2017-11-16 Thread Matt Schepers
I would like to filter out two configure flags from EXTRA_OECONF in a .bbappend. When I filter out only one everything works, when I do the same thing twice it doesn't. Here is the .bbappend that works: EXTRA_OECONF := "${@oe_filter_out('--with-term=rxvt', '${EXTRA_OECONF}', d)}" EXTRA_OE

[yocto] tiny-linux distribution with raspberrypi error

2017-11-16 Thread Sherif Omran
hi i am trying to compile the yocto-tiny for raspberry pi by adding the distro to my local.conf DISTRO = "poky-tiny" and i get the following ERROR: nothing provides 'virtual/kernel' ERROR: linux-yocto-tiny Provides virtual/kernel but was skipped: incompatible with machine raspberrypi0-wifi (n

Re: [yocto] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Leonardo Sandoval
isn't it this class meta/classes/insane.bbclass for this type of checks? On Thu, 16 Nov 2017 15:05:56 + Martyn Welch wrote: > Sometimes we wish to ensure that files or directories are not installed > somewhere that may prove detrimental to the operation of the system. For > example, this ma

Re: [yocto] Detecting all AUTOREV usages in a build, for reproducible stable production builds.

2017-11-16 Thread Paul Knopf
That is EXACTLY what I am looking for. Thanks! A "nice to have" would be a check to see if any AUTOREVs has snuck in since last srcrev.conf generation. I'd like to validate/ensure this with a build task on the build server. On Thu, Nov 16, 2017 at 10:18 AM Leonardo Sandoval < leonardo.sandoval.go

Re: [yocto] [OE-core] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Otavio Salvador
On Thu, Nov 16, 2017 at 1:05 PM, Martyn Welch wrote: > Sometimes we wish to ensure that files or directories are not installed > somewhere that may prove detrimental to the operation of the system. For > example, this may be the case if files are placed in a directory that is > utilised as a mount

Re: [yocto] Detecting all AUTOREV usages in a build, for reproducible stable production builds.

2017-11-16 Thread Leonardo Sandoval
On Thu, 16 Nov 2017 05:06:30 -0500 Paul Knopf wrote: > I want to store/fix AUTOREV values for production builds. I saw > BB_CACHE_POLICY, but the format (sqllite) isn't something that can be > checked in. > > Let's say I have an image: > > bitbake my-image > > How do I detect any dependency th

[yocto] [PATCH v4 2/3] core-image.bbclass: add default IMAGE_QA_PROHIBIT_PATHS variable

2017-11-16 Thread Martyn Welch
Add a default IMAGE_QA_PROHIBIT_PATHS variable containing paths known to be mounted in the default fstab, which are known mount points or directories which should be populated at runtime. Suggested-by: Alexander Kanavin Signed-off-by: Martyn Welch --- Changes since v3: - This patch added. me

[yocto] [PATCH v4 3/3] ref-manual: Add documentation for prohibited-path QA test

2017-11-16 Thread Martyn Welch
Add documentation for the IMAGE_QA_PROHIBITED_PATHS variable and associated prohibited-path QA test Signed-off-by: Martyn Welch --- Changes since v1: - Correcting author and SOB. Changes since v2: - Reimplemented as image rather than package level QA test, altering documentation to suit. -

[yocto] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Martyn Welch
Sometimes we wish to ensure that files or directories are not installed somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed in a directory that is utilised as a mount point at run time, thus making them inaccessible once when th

Re: [yocto] [meta-swupd][PATCH] layer.conf: exclude libarchive (bsdtar) dependency from swupd-client

2017-11-16 Thread Patrick Ohly
On Thu, 2017-11-16 at 10:02 +, André Draszik wrote: > From: André Draszik > > The swupd-client doesn't need to be rebuilt if libarchive > changes, because swupd-client just invokes the command line > utility bsdtar from the libarchive recipe, it doesn't link > against libarchive. > The bsdtar

[yocto] SWIG, python, native gcc and multiarch

2017-11-16 Thread Anton Gerasimov
Hi all, I'm trying to run a piece of SWIG code while building u-boot (namely compiling it with BUILD_ROM=y, which requires pylibfdt which is built with a SWIG interface file and a setup.py). I'm having a problem that the SWIG setup.py script for a reason I don't quite understand instead of compili

[yocto] qt4 sdk problem on rocko

2017-11-16 Thread Belisko Marek
Hi, I'm porting our layers to latest rocko release. I build SDK to be able to crosscompile our cmake based application which is using qt4. To have qt4-tool in sdk I've added: TOOLCHAIN_HOST_TASK_append = " nativesdk-qt4-tools" Then in app CMakelists.txt I've use include(FindQt4) but it's barking

Re: [yocto] [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Alexander Kanavin
On 11/15/2017 05:10 PM, Martyn Welch wrote: Sometimes we wish to ensure that files or directories are not installed somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed in a directory that is utilised as a mount point at run ti

Re: [yocto] [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Martyn Welch
On Wed, 2017-11-15 at 18:46 -0200, Otavio Salvador wrote: > On Wed, Nov 15, 2017 at 1:10 PM, Martyn Welch > wrote: > > Sometimes we wish to ensure that files or directories are not installed > > somewhere that may prove detrimental to the operation of the system. For > > example, this may be the c

[yocto] Detecting all AUTOREV usages in a build, for reproducible stable production builds.

2017-11-16 Thread Paul Knopf
I want to store/fix AUTOREV values for production builds. I saw BB_CACHE_POLICY, but the format (sqllite) isn't something that can be checked in. Let's say I have an image: bitbake my-image How do I detect any dependency that is using AUTOREV? I'd like to generate a dynamic.conf file that fixes

Re: [yocto] [meta-swupd][PATCH] layer.conf: exclude libarchive (bsdtar) dependency from swupd-client

2017-11-16 Thread André Draszik
On Thu, 2017-11-16 at 10:02 +, André Draszik wrote: > From: André Draszik > > The swupd-client doesn't need to be rebuilt if libarchive > changes, because swupd-client just invokes the command line > utility bsdtar from the libarchive recipe, it doesn't link > against libarchive. > The bsdtar

[yocto] [meta-swupd][PATCH] layer.conf: exclude libarchive (bsdtar) dependency from swupd-client

2017-11-16 Thread André Draszik
From: André Draszik The swupd-client doesn't need to be rebuilt if libarchive changes, because swupd-client just invokes the command line utility bsdtar from the libarchive recipe, it doesn't link against libarchive. The bsdtar binary changing doesn't matter, as bsdtar's ABI (command line argumen

Re: [yocto] [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Martyn Welch
On Wed, 2017-11-15 at 18:46 -0200, Otavio Salvador wrote: > On Wed, Nov 15, 2017 at 1:10 PM, Martyn Welch > wrote: > > Sometimes we wish to ensure that files or directories are not installed > > somewhere that may prove detrimental to the operation of the system. For > > example, this may be the c