[yocto] Adding Static Library Support to the SDK or Rootfs

2017-04-04 Thread Life Life
Hello, I'm try to build static library for SDK. Update the *build*/local.conf file with the following information SDKIMAGE_FEATURES = "staticdev-pkgs dev-pkgs" *INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "0" BUILDHISTORY_FEATURES = "sdk"* *But cannot create static library for SDK. * *T

Re: [yocto] FIT Image boot issue

2017-04-04 Thread Gujulan Elango, Hari Prasath (H.)
Sorry the its file was blocked by Outlook. Renamed the extension and re-attaching it. Regards, Hari Prasath From: Gujulan Elango, Hari Prasath (H.) Sent: Tuesday, April 04, 2017 7:39 PM To: yocto@yoctoproject.org Cc: Rajagopalan, Thiagarajan (T.); Vadivel, Arulpandiyan (A.); Ravindran, Madhusud

Re: [yocto] IoTivity on Yocto project

2017-04-04 Thread Khem Raj
On Mon, Apr 3, 2017 at 10:10 AM, Natalia Theologou wrote: > Hello, > > > I need a help here. > > Is it possible to add to an existing image created with Yocto project the > IoTivity? Maybe bitbake the IoTivity layer to rpm? > > Is it necessary to make an image including IoTivity? > > > Please if a

[yocto] IoTivity on Yocto project

2017-04-04 Thread Natalia Theologou
Hello, I need a help here. Is it possible to add to an existing image created with Yocto project the IoTivity? Maybe bitbake the IoTivity layer to rpm? Is it necessary to make an image including IoTivity? Please if anyone knows I would like a help. Thanks in advance. Natalia -- _

[yocto] runqemu - "Could not initialize SDL(No available video device) - exiting"

2017-04-04 Thread Martin Kelly
Hi, I'm hitting an error on runqemu when I try to build an SDK and image on one machine and run it on another, even when the build machine and qemu-running machine match very closely (both running Debian Jessie on Intel 64-bit hardware). Specifically, I get this error: Could not initialize S

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: waveshare screen support

2017-04-04 Thread Trevor Woerner
I see what happened... knowing that I needed those lines set, my bbappend didn't have the "if" line, it simply applied the lines without the check. The check was added when pushing upstream just in case somebody didn't want those lines in their config :-) I should have tested more extensively after

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: waveshare screen support

2017-04-04 Thread Trevor Woerner
Odd... I've been carrying this patch for a month and haven't had issues :-( On Tue, Apr 4, 2017 at 8:50 AM, Andrei Gherzan wrote: > > > On 4 April 2017 13:48:53 BST, Andrea Galbusera wrote: >>On Tue, Apr 4, 2017 at 12:17 PM, Andrei Gherzan >>wrote: >> >>> Hi, >>> >>> On 4 April 2017 09:48:32 BS

Re: [yocto] Enforcing version constraints on dependencies at build-time

2017-04-04 Thread Burton, Ross
On 4 April 2017 at 21:26, Matt Hoosier wrote: > Is there any way to escape that isolation and express version boundaries? > You're right, the recipe isolation means you can't do this from inside a recipe's contet. I'd like to see bitbake actually verify that the version constraints are satisfie

[yocto] Enforcing version constraints on dependencies at build-time

2017-04-04 Thread Matt Hoosier
The RDEPENDS variable supports giving numeric version bounds. For example: RDEPENDS_${PN} = "foo (>= 1.3)" That works well for getting version dependencies respected at rootfs time. But DEPENDS (used at build-time) silently ignores any similar constraint arguments. For example: DEPENDS = "fo

[yocto] [qa-tools][PATCH] full-test-cycle-wrapper: Correct typos

2017-04-04 Thread jose . perez . carranza
From: Jose Perez Carranza Update name of ENVIRONMETS to ENVIRONMENTS and update the ENVIRONMENTS value for runtime component Signed-off-by: Jose Perez Carranza --- scripts/full-test-cycle-wrapper.sh | 44 +++--- 1 file changed, 22 insertions(+), 22 deletions(-)

[yocto] [qa-tools][PATCH] full-test-cycle-wrapper: Correct qemu-auto variables

2017-04-04 Thread jose . perez . carranza
From: Jose Perez Carranza Update variables for creating test runs for qemu ato component Signed-off-by: Jose Perez Carranza --- scripts/full-test-cycle-wrapper.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/full-test-cycle-wrapper.sh b/scripts/full-test-cyc

[yocto] [meta-raspberrypi][PATCH v2] rpi-config: fix invalid shell variable name

2017-04-04 Thread Andrea Galbusera
Commit da32aac introduced an invalid shell variable name in do_deploy(): according to bash manpage variable names cannot contain dots. Replace dot with underscore to fix it. Signed-off-by: Andrea Galbusera --- v2: also update README accordingly Signed-off-by: Andrea Galbusera --- README

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: fix invalid shell variable name

2017-04-04 Thread Paul Barker
On Tue, 4 Apr 2017 16:18:03 +0200 Andrea Galbusera wrote: > Commit da32aac introduced an invalid shell variable name in do_deploy(): > according to bash manpage variable names cannot contain dots. Replace > dot with underscore to fix it. > > Signed-off-by: Andrea Galbusera > --- > recipes-bsp

[yocto] [[PATCH][yocto-autobuilder]] nightly-oe-selftest.conf: Remove set of SANITY_TESTED_DISTROS

2017-04-04 Thread Aníbal Limón
The sanity testing was disabled for all builds into CreateAutoConf buildstep so atextappend isn't need now. [1] [1] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=87b10595e9a1d36081ec60d3069f4a98798f27eb Signed-off-by: Aníbal Limón --- buildset-config.controller/nightly

[yocto] [patchwork][PATCH] parsemail.py: Improve clean_subject function

2017-04-04 Thread Jose Lamego
PATCH prefix is not appropriately identified as such if it is not sepparated from following word in an email Subject line. This leads to wrong patch naming. This change allows for appropriate patch naming by checking during clean_subject function if "PATCH" prefix in Subject line is not sepparated

[yocto] Minutes: Yocto Project Technical Team Meeting

2017-04-04 Thread Jolley, Stephen K
Attendees: Stephen, Armin, Richard, Stephano, Joshua, Mark, Saul, Randy, Ross, TLwoerner, Svein, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) YP 2.3 M3 rc2 is in QA - https://wiki.yoctoproject.org/wiki/2.3_QA_Status#Summary_Report. We believe we h

[yocto] [meta-qt4][PATCH] qt4: disable openssl support

2017-04-04 Thread Alexander Kanavin
Qt4 does not support openssl 1.1 (and likely never will), while its oe-core dependencies are being moved to that version, which is causing a sysroot conflict between openssl 1.0 and 1.1 headers. The only way to resolve it is to disable openssl support in Qt4, as we don't want Qt4's outdated version

[yocto] [meta-raspberrypi][PATCH] rpi-config: fix invalid shell variable name

2017-04-04 Thread Andrea Galbusera
Commit da32aac introduced an invalid shell variable name in do_deploy(): according to bash manpage variable names cannot contain dots. Replace dot with underscore to fix it. Signed-off-by: Andrea Galbusera --- recipes-bsp/bootfiles/rpi-config_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 dele

[yocto] [meta-security][V2][PATCH] apparmor: update to 2.11.0 plus ptest

2017-04-04 Thread Armin Kuster
update to 2.11 Add basic ptest support v2: remove none existent file Signed-off-by: Armin Kuster --- recipes-security/AppArmor/apparmor_2.10.95.bb | 116 recipes-security/AppArmor/apparmor_2.11.0.bb | 126 ++ recipes-security/AppArmor/files/run-

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: waveshare screen support

2017-04-04 Thread Andrei Gherzan
On 4 April 2017 13:48:53 BST, Andrea Galbusera wrote: >On Tue, Apr 4, 2017 at 12:17 PM, Andrei Gherzan >wrote: > >> Hi, >> >> On 4 April 2017 09:48:32 BST, Andrea Galbusera >wrote: >> >On Fri, Mar 24, 2017 at 6:49 PM, Trevor Woerner >> >wrote: >> > >> >> Add support for the Waveshare 1024x600

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: waveshare screen support

2017-04-04 Thread Andrea Galbusera
On Tue, Apr 4, 2017 at 12:17 PM, Andrei Gherzan wrote: > Hi, > > On 4 April 2017 09:48:32 BST, Andrea Galbusera wrote: > >On Fri, Mar 24, 2017 at 6:49 PM, Trevor Woerner > >wrote: > > > >> Add support for the Waveshare 1024x600 "C" Rev2.1 7" IPS Capacitive > >Touch > >> Screen LCD with HDMI int

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: waveshare screen support

2017-04-04 Thread Andrei Gherzan
Hi, On 4 April 2017 09:48:32 BST, Andrea Galbusera wrote: >On Fri, Mar 24, 2017 at 6:49 PM, Trevor Woerner >wrote: > >> Add support for the Waveshare 1024x600 "C" Rev2.1 7" IPS Capacitive >Touch >> Screen LCD with HDMI interface: >> >> http://www.waveshare.com/7inch-HDMI-LCD-C.htm >>

Re: [yocto] Custom conf files

2017-04-04 Thread Patrick Ohly
On Tue, 2017-04-04 at 10:23 +0200, Jaap de Jong wrote: > Hi, > > I'm just wondering what the best practise is for configuration files > that I want to change for a specific image. > > F.i. a simple one: /etc/issue We just debated the exact same question over on the refkit mailing list, without

Re: [yocto] [meta-raspberrypi][PATCH] rpi-config: waveshare screen support

2017-04-04 Thread Andrea Galbusera
On Fri, Mar 24, 2017 at 6:49 PM, Trevor Woerner wrote: > Add support for the Waveshare 1024x600 "C" Rev2.1 7" IPS Capacitive Touch > Screen LCD with HDMI interface: > > http://www.waveshare.com/7inch-HDMI-LCD-C.htm > http://www.waveshare.com/wiki/7inch_HDMI_LCD_(C) > > This produc

[yocto] Custom conf files

2017-04-04 Thread Jaap de Jong
Hi, I'm just wondering what the best practise is for configuration files that I want to change for a specific image. F.i. a simple one: /etc/issue I could create a bbappend for the responsible recipe. Or I could add a ROOTFS_POSTPROCESS_COMMAND and patch in my changes Are there other optio