[yocto] MACHINE .conf file

2018-04-09 Thread Raymond Yeung
Some questions about MACHINE: 1. I'd customized MACHINE (="intel-corei7-64") variable in conf/local.conf under my build directory, as per document, and had successfully generated an image for my H/W. However, I don't seem to find "intel-corei7-64.conf" file in meta/conf/machine under poky sour

Re: [yocto] pyro: missing ldconfig

2018-04-09 Thread Andre McCurdy
On Thu, Apr 5, 2018 at 11:53 PM, Florian Doersch wrote: > > I recently updated from pyro 2.3.3 to latest pyro branch for my raspberry3 > and ran into the following problem > ... > The problem does not occur when using the latest pyro tag (yocto-2.3.3) Unless someone else has a better answer, you

Re: [yocto] How to set SRC_URI in local.conf / how to set any variable of a specific recipe in local.conf

2018-04-09 Thread Andre McCurdy
On Sat, Apr 7, 2018 at 8:04 AM, Jakob Hasse wrote: > > how can I set a another branch, i.e., the SRC_URI variable for a specific > recipe in conf/local.conf? Or more general: how can I change the variable of > any recipe in local.conf temporarily? I tried something like this already: > SRC_ = "...

Re: [yocto] Yocto Project Status WW15’18

2018-04-09 Thread akuster808
On 04/09/2018 08:13 AM, Jordan, Robin L wrote: > > Current Dev Position: YP 2.5 M4 final close out. > > Next Deadline: YP 2.5 M4 release is 4/27/18 > >   > > SWAT Team Rotation: > > SWAT lead is currently: Paul. > > SWAT team rotation: Paul -> Tracy on April 13, 2018 > > SWAT team rotation: Tracy

[yocto] Offline use of opkg

2018-04-09 Thread Sebastian Rohde
Hello everybody, in my setup opkg is used as the package manager and I use it to install / uninstall several software alternatives. I want this to work on deployed devices in an offline fashion, i.e. I want to do "opkg install " without internet access. might or might not be installed in the

[yocto] Yocto Project Status WW15’18

2018-04-09 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M4 final close out. Next Deadline: YP 2.5 M4 release is 4/27/18 SWAT Team Rotation: SWAT lead is currently: Paul. SWAT team rotation: Paul -> Tracy on April 13, 2018 SWAT team rotation: Tracy -> Stephano on April 20, 2018 https://wiki.yoctoproject.org/wiki/Yocto_

Re: [yocto] meta-virtualization -> docker not packaged when using PACKAGE_CLASSES ?= "package_deb"

2018-04-09 Thread Bruce Ashfield
On 04/06/2018 09:13 AM, Mark Junghanns wrote: Hello, I encountered a funny behavior the other day. While trying to integrate Docker into my image using the openembedded meta-virtualization layer, I happened to not being able to get my image finalized. Usually I build with PACKAGE_

Re: [yocto] [meta-java][PATCH 0/3] Java CA certificates updates

2018-04-09 Thread Maxin B. John
Hi, On Fri, Mar 30, 2018 at 09:40:16AM +0100, André Draszik wrote: > openjdk-8 and openjre-8 use a trustStore that has nothing to do with > the system trusted CA certificates as provided by the ca-certificates > package. > > These patches fix both to use the system CA certificates instead. > > T

Re: [yocto] [yocot] bluez5 not included in image

2018-04-09 Thread John, Maxin
Hi, bluetoothd generally get installed here: /usr/libexec/bluetooth/bluetoothd You should probably update the PATH or use absolute path to invoke bluetoothd. Best Regards, Maxin From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Sherif Omran Sent: Monday,

[yocto] [yocot] bluez5 not included in image

2018-04-09 Thread Sherif Omran
In local.conf i have DISTRO_FEATURES_append += " bluez5 bluetooth wifi" IMAGE_INSTALL_append += " linux-firmware-bcm43430 bluez5 bridge-utils wpa-supplicant python-smbus i2c-tools " and when i run bluetoothd -v it is not found it seems for some reason bluez5 is not included. -- ___

[yocto] QA cycle report for 2.5 M3 RC1

2018-04-09 Thread Yeoh, Ee Peng
Hello All, This is the full report for 2.5 M3 RC1: https://wiki.yoctoproject.org/wiki/WW15_-_2018-04-09-_Full_Test_Cycle_-_2.5_M3_rc1 === Summary The QA cycle for release 2.5 M3 RC1 was completed.  Team had discovered 7 new bugs. There were 3 bugs related to runtime [4] [6] [7],