[yocto] [Yocto] Enable a recipe/package only when other dependent recipe/package is part of image.

[Amarnath Valluri]

Hello,

I have my own layer, that provides configuration packages for core Linux 
components, for example ‘connman-conf’ for ‘connman’ package.


I would like to provide a pakcagegroup-config, that should automatically 
select the configuration packages that are part of image configuration. 
Say if ‘connman’ is part of image then it should add ‘connman-conf’ to 
its RDEPENDS_${PN}.



For this I tried to use ‘oe.packagedata.pkgmap’, to check if the core 
component exists as below:




def check_if_enabled(comp, trueval, d):

   import oe.packagedata

   pkgmap = oe.packagedata.pkgmap(d)

  if pkgmap is not None and pkgmap.get(comp) is not None:
 return trueval

   return “”

RDEPENDS_${PN} = “ \
   ${@check_if_enabled(“connman”, “connman-conf”, d)} \
“

---

This works as expected when the packagedata is available, i.e., image is 
build at least once first, then my layer is added to BBLAYERS and then 
rebuild the image.


But this fails when there is no packagedata cache available.

Can someone help me to resolve this properly.


Thanks,
Amarnath

-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 


This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   Version   Upstream version  Maintainer   
NoUpgradeReason
      ---  
--
texinfo   6.0   6.1   Alejandro Hernandez
ruby  2.2.2 2.3.0 Alejandro Hernandez
perl  5.22.15.24.0Alejandro Hernandez
python-dbus   1.2.0 1.2.4 Alejandro Hernandez
python-git1.0.2 2.0.1 Alejandro Hernandez
python-mako   1.0.3 1.0.4 Alejandro Hernandez
python-numpy  1.10.41.11.0Alejandro Hernandez
python-pygobject  3.18.23.20.0Alejandro Hernandez
python-scons  2.4.1 2.5.0 Alejandro Hernandez
python3-pip   8.0.0 8.1.1 Alejandro Hernandez
python3-setuptools19.4  20.9.0Alejandro Hernandez
python-setuptools 19.4  20.9.0Alejandro Hernandez
perl-native   5.22.15.24.0Alejandro Hernandez
python-scons-native   2.4.1 2.5.0 Alejandro Hernandez
liberation-fonts  1.04  2.00.1Alexander Kanavin
2.x depends on fontforge pa...
gcr   3.18.03.20.0Alexander Kanavin
gnome-desktop33.18.23.20.1Alexander Kanavin
libsecret 0.18.40.18.5Alexander Kanavin
watchdog  5.14  5.15  Alexander Kanavin
kexec-tools   2.0.112.0.12Alexander Kanavin
btrfs-tools   4.4   4.5.1 Alexander Kanavin
sysprof   1.2.0+gitX3.20.0+gitAUTOINC...  Alexander Kanavin
systemtap-uprobes 2.9   3.0   Alexander Kanavin
systemtap 2.9   3.0   Alexander Kanavin
epiphany  3.18.43.20.1Alexander Kanavin
hwlatdetect   0.96  0.97  Alexander Kanavin
rt-tests  0.96  0.97  Alexander Kanavin
webkitgtk 2.10.72.12.1Alexander Kanavin
gnutls3.4.9 3.4.11Alexander Kanavin
icu   56.1  57.1  Alexander Kanavin
nss   3.21  3.23  Alexander Kanavin
babeltrace1.3.1 1.3.2 Alexander Kanavin
libarchive3.1.2 3.1.901a  Alexander Kanavin
msmtp 1.6.3 1.6.4 Alexander Kanavin
mkelfimage4.0+gitX  4.3+gitAUTOINC+1b...  Alexander Kanavin
mkelfimage has been removed...
iso-codes 3.65  3.67  Alexander Kanavin
apt   1.0.10.1  1.2.10Aníbal Limón
qemu  2.5.0 2.5.1 Aníbal Limón
pinentry  0.9.2 0.9.7 Armin Kuster
linux-libc-headers4.4   4.5.2 Bruce Ashfield
guilt-native  0.35+gitX 0.36+gitAUTOINC+2...  Bruce Ashfield
dbus-test 1.10.61.10.8Chen Qi
dbus  1.10.61.10.8Chen Qi
util-linux2.27.12.28  Chen Qi
curl  7.47.17.48.0Chen Qi
byacc 20150711  20160324  Chen Qi
gzip  1.6   1.7   Chen Qi
sudo  1.8.151.8.16Chen Qi
sysstat   11.2.011.3.3Chen Qi
grep  2.23  2.25  Chen Qi
build-appliance-i...  14.0.014.0.1Cristian Iorga
dhcp  4.3.3 4.3.4 Hongxu Jia
ncurses   6.0+20160213  6.0+20160319  Hongxu Jia
pax-utils 1.1.5 1.1.6 Hongxu Jia
createrepo0.4.110.10.4Hongxu Jia   
Versions after 0.9.* use YU...
libgcrypt 1.6.5 1.7.0 Hongxu Jia
man-pages 4.04  4.05  Hongxu Jia
libnewt-python0.5

Re: [yocto] [OE-core] Yocto Project Status WW17

[Trevor Woerner]

On Fri 2016-04-22 @ 08:29:19 PM, Burton, Ross wrote:
> On 22 April 2016 at 18:04, Trevor Woerner  wrote:
> >
> > Have the eSDK and CROPS projects been announced publicly? Are they
> available
> > for us to "play with"?
> 
> 
> eSDK is the "extensible SDK', or what appears when you do bitbake image -c
> populate_sdk_ext.  This should be in the manual already, the tl;dr is that
> its an SDK you can manipulate after installation.

Thanks for the update.

> CROPS is docker magic to do builds on Windows/Mac.  Todor did a
> presentation at ELC: http:
> //events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf
> 

I was *very* excited to learn about CROPS at ELC, which is why I was wondering
if it was available to experiment with somewhere?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Customize login prompt text in Yocto

[Rudolf Streif]

>
> the information shown is from the file /etc/issue. You can for example do
> post-processing on this file and change the information. You can add this
> to your image recipe.
>
> update_issue() {
> echo "Your text" > ${IMAGE_ROOTFS}/etc/issue
> }
>
> ROOTFS_POSTPROCESS_COMMAND += " update issue; "
>


The more "yoctonic" way of setting this is to modify the DISTRO_NAME
variable, which is set in the distro configuration file e.g. poky.conf. If
you are building your own distro it you may want to derive your own distro
configuration file from the ones that Poky provides. There you can also set
other variables such as DISTRO_VERSION, MAINTAINER, etc.

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

Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++

[Julien Gueytat]

Hi,

you will find here two patches to get EGL enabled on RaspberryPi without 
any hack in meta-*bsp layers.
Please note that it is just a proposition of correction as I'm not aware 
of the best correction you would like to implement.


The result of those two patches on top of master for meta-raspberry and 
krogoth for meta-qt5 (jethro would have been the same correction) gives:

  QPA backends:
DirectFB . no
EGLFS  yes
  EGLFS i.MX6  no
  EGLFS i.MX6 Wayland. no
  EGLFS EGLDevice  no
  EGLFS GBM .. no
  EGLFS Mali . no
  EGLFS Raspberry Pi . yes
  EGLFS X11 .. no

As long as I understand there use to be a lot of hacks in either BSP 
layers or mkspecs files for Qt.
With proper pkg_config files we might have a simpler solution. Right now 
I'm quite sure that the master branch from Qt has some troubles to 
handle pkg-config stuff AND mkspecs at the same time. There is a bug 
report opened on that subject.


The patch on meta-qt5 is to "force" layers to implement pkg-config 
files. (I just did it for EGL...) As I said it's not a full rewrite of 
the configure file at all.
The patch on the Raspberry is just to add one library missing to get the 
EGLFS Raspberry Pi test passing (the EGL test one was already working 
with this meta-qt5 patch)


Best Regards,


Le 21/04/2016 19:10, Andrei Gherzan a écrit :

Hi Julien,

On Thu, Apr 21, 2016 at 10:15:23AM +0200, Julien Gueytat wrote:

Just to keep you informed that a bug report has been opened to Qt:
https://bugreports.qt.io/browse/QTBUG-52739

We might save some patches in layers by solving this,
Thanks for helping,


Great Julien. Here is a hint - would this help your problem?
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028277.html


Le 20/04/2016 01:46, Julien Gueytat a écrit :

Hi again guys,

after more investigations:

I found out that the default value -lEGL comes from
./mkspecs/common/linux.conf which is included in
./mkspecs/linux-oe-g++/qmake.conf

linux-oe-g++ being the only generic mkspecs that should be used in Yocto

So! At the time the configuration enters egl.pro the content of the
variables LIBS and QMAKE_EGL_LIBS are still a bit weird for me :

1- LIBS already has the content of the QMAKE_EGL_LIBS content from the
result of the pkg-config command.
2- QMAKE_EGL_LIBS has the content of the default value found in
./mkspecs/common/linux.conf

There are two options to have it properly working:
- First and easy option : remove the QMAKE_EGL_LIBS default variable in
./mkspecs/linux-oe-g++/qmake.conf since the good libs seems to already
been present in the LIBS variable.
- Second option : understand why the LIBS variable is already properly
set and why the QMAKE_EGL_LIBS properly computed in the configure and
present .qmake.vars is not used. (I would say that the device spec
overrides the one from qmake spec... I did not dig further yet.)

Anyway I'm pretty sure the trouble comes from meta-qt5 side now. I'm
pretty sure meta-raspberrypi maintainers can confirm that their master
branch handles pkg-config stuff now.

Thanks advance for having a look on this guys,
Best Regards


Le 19/04/2016 10:46, Julien Gueytat a écrit :

Hi,

I still can't figure out the patch to apply in meta-qt5 to get EGL
support with the Raspberry.

The test to check EGL does not pass and fails with the following command:

arm-poky-linux-gnueabi-g++  -march=armv7-a -marm -mthumb-interwork
-mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 
--sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o
-lGLESv2 -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL


Here is the content of the file egl.pro:

$ cat egl.pro
SOURCES = egl.cpp

for(p, QMAKE_LIBDIR_EGL) {
 exists($$p):LIBS += -L$$p
}

message("In egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
message("In egl.pro - 1: LIBS = $$LIBS")

!isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH += $$QMAKE_INCDIR_EGL
!isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL

message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
message("In egl.pro - 2: LIBS = $$LIBS")

CONFIG -= qt

In the main ./configure file of qtbase:

| In configure #1: QMAKE_LIBS_EGL =
| In configure #2: QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host
-lvchostif -lbcm_host -lvcos -lvchiq_arm -pthread

The variable QMAKE_LIBS_EGL is set properly.


In the ./config.tests/qpa/egl/egl.pro file:

| Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL
| Project MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host
-lvchostif -lvcos -lvchiq_arm -pthread
| Project MESSAGE: In egl.pro - 2: QMAKE_LIBS_EGL = -lEGL
| Project MESSAGE: In egl.pro - 2: LIBS = -lEGL -lGLESv2 -lbcm_host
-lvchostif -lvcos -lvchiq_arm -pthread -lEGL


*What I see is that:*
In the configure file the variable QMAKE_LIBS_EGL is properly set
through pkg-config.
In the egl.pro file... The variable LIBS ge

Re: [yocto] Customize login prompt text in Yocto

[Andreas Enbacka]

Hi Peter,

Thanks a lot for the info, I will try it out.

Regards,
Andreas

> 24 apr. 2016 kl. 11:06 skrev Peter Bergin :
> 
> Hi,
> 
>> On 04/24/2016 09:42 AM, Andreas Enbacka wrote:
>> Hello,
>>  
>> Normally, when building e.g., a console-based image using Yocto, you will 
>> get at caption text ”Poky Reference Distribution”... at the login prompt. Is 
>> it easily possible to change / customize this caption text,
>> and in such a case, which Yocto package / recipe requires change. Any 
>> information would be greatly appreciated.
>>  
>> Best regards,
>> Andreas Enbacka
> 
> the information shown is from the file /etc/issue. You can for example do 
> post-processing on this file and change the information. You can add this to 
> your image recipe.
> 
> update_issue() {
> echo "Your text" > ${IMAGE_ROOTFS}/etc/issue
> }
> 
> ROOTFS_POSTPROCESS_COMMAND += " update issue; "
> 
> Best regards,
> /Peter
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Customize login prompt text in Yocto

[Peter Bergin]

Hi,

On 04/24/2016 09:42 AM, Andreas Enbacka wrote:
Hello,

Normally, when building e.g., a console-based image using Yocto, you will get 
at caption text ”Poky Reference Distribution”... at the login prompt. Is it 
easily possible to change / customize this caption text,
and in such a case, which Yocto package / recipe requires change. Any 
information would be greatly appreciated.

Best regards,
Andreas Enbacka

the information shown is from the file /etc/issue. You can for example do 
post-processing on this file and change the information. You can add this to 
your image recipe.

update_issue() {
echo "Your text" > ${IMAGE_ROOTFS}/etc/issue
}

ROOTFS_POSTPROCESS_COMMAND += " update issue; "

Best regards,
/Peter
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Customize login prompt text in Yocto

[Andreas Enbacka]

Hello,

 

Normally, when building e.g., a console-based image using Yocto, you will
get at caption text "Poky Reference Distribution"... at the login prompt. Is
it easily possible to change / customize this caption text,

and in such a case, which Yocto package / recipe requires change. Any
information would be greatly appreciated.

 

Best regards,

Andreas Enbacka

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