Re: building under Centos 6.3
Paul Eggleton
On Tuesday 09 October 2012 16:18:05 Jim Abernathy wrote:
Just an FYI, following the Getting Started Guide for CentosYou're right - in the documentation for the last release, inexplicably this one was missed out. Fortunately though the new version of the Quick Start Guide for 1.3 in which that section has been rewritten does however include chrpath in the list of packages for CentOS. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre
|
|
Control which host components are included in ADT output?
Evade Flow <evadeflow@...>
I have a question about the ADT and how it selects host SDK components.
If I type: % bitbake meta-toolchain-sdk I wind up getting hundreds of target libs when I extract the generated tarball: % pwd /opt/poky/1.2.1/sysroots % ls armv5te-poky-linux-gnueabi/usr/lib | wc -l 696 but a relatively small number of host libs: % ls i686-pokysdk-linux/usr/lib | wc -l 53 Is this normal? Taking libxml2 as an example: % ls -1 armv5te-poky-linux-gnueabi/usr/lib/libxml* armv5te-poky-linux-gnueabi/usr/lib/libxml2.la armv5te-poky-linux-gnueabi/usr/lib/libxml2.so armv5te-poky-linux-gnueabi/usr/lib/libxml2.so.2 armv5te-poky-linux-gnueabi/usr/lib/libxml2.so.2.7.8 % ls -1 i686-pokysdk-linux/usr/lib/libxml* zsh: no matches found: i686-pokysdk-linux/usr/lib/libxml* It seems desirable to have libxml2 be part of the SDK I give to my development team. We have a lot of test applications that can be run on the host, and I don't like the thought of somebody wasting time chasing a bug that turns out to be due to the fact that he is linking against a different (system-installed) version of libxml2 rather than the target version. Skimming the ADT manual, this section seems to hint at a solution: - http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#adt-package But I can't quite follow all the steps. :-% It says (using libglade as an example): First, you should generate the ipk file for the libglade package and add it into a working opkg repository. Use these commands: $ bitbake libglade $ bitbake package-index Being totally new to opkg, this lost me. What does the 'package-index' target actually do? Does bitbake "add it [libglade] into a working opkg repository" for me, or am I supposed to take the output of the command and do something with it? I had a look in these two locations for 'package-index' and came up empty: - http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html - http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html What's the best place to look for these kinds of references when I get stuck on something? The ADT docs go on to say: Next, source the environment setup script found in the Yocto Project files. Follow that by setting up the installation destination to point to your sysroot as <sysroot_dir>. Finally, have an OPKG configuration file <conf_file> that corresponds to the opkg repository you have just created. $ opkg-cl –f <conf_file> -o <sysroot_dir> update $ opkg-cl –f <cconf_file> -o <sysroot_dir> \ --force-overwrite install libglade $ opkg-cl –f <cconf_file> -o <sysroot_dir> \ --force-overwrite install libglade-dbg $ opkg-cl –f <conf_file> -o <sysroot_dir> \ --force-overwrite install libglade-dev <sysroot_dir> I understand, but what is <conf_file>? Did bitbake generate this for me? Am I supposed to create one by hand? Where? These instructions are a little hard to follow due to the use of placeholders rather than concrete arguments. I think a complete, explicit example would help a lot here. Also, it seems likely that the above commands would only install a libglade compiled for the target? How would I generate a libglade for the host? Another question is: is there a way to tune the ADT tarball to be a better fit for my needs so that I don't need to add so many packages by hand after-the-fact? Any advice much appreciated, thanks!
|
|
[PATCH 5/5] update maintainers of various BSPs
nitin.a.kamble@...
From: Nitin A Kamble <nitin.a.kamble@...>
Nitin has taken over maintainership from Tom for these BSPs sugarbay, emenlow, crownbay, jasperforest, chiefriver Signed-off-by: Nitin A Kamble <nitin.a.kamble@...> --- MAINTAINERS | 12 ++++++------ meta-chiefriver/README | 11 +++++++++++ meta-crownbay/README | 2 +- meta-emenlow/README | 2 +- meta-jasperforest/README | 2 +- meta-sugarbay/README | 2 +- 6 files changed, 21 insertions(+), 10 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 3bf0add..d63ed31 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -37,15 +37,15 @@ M: Kishore Bodke <kishore.k.bodke@...> F: meta-cedartrail/ CHIEFRIVER -M: Tom Zanussi <tom.zanussi@...> +M: Nitin A Kamble<nitin.a.kamble@...> F: meta-chiefriver/ COMMON -M: Tom Zanussi <tom.zanussi@...> +M: Nitin A Kamble<nitin.a.kamble@...> F: common/recipes-core/ CROWNBAY -M: Tom Zanussi <tom.zanussi@...> +M: Nitin A Kamble<nitin.a.kamble@...> F: meta-crownbay/ CRYSTALFOREST @@ -53,7 +53,7 @@ M: Kishore Bodke <kishore.k.bodke@...> F: meta-crystalforest/ EMENLOW -M: Tom Zanussi <tom.zanussi@...> +M: Nitin A Kamble<nitin.a.kamble@...> F: meta-emenlow/ FRI2 @@ -61,7 +61,7 @@ M: Darren Hart <dvhart@...> F: meta-fri2/ JASPERFOREST -M: Tom Zanussi <tom.zanussi@...> +M: Nitin A Kamble<nitin.a.kamble@...> F: meta-jasperforest/ N450 @@ -73,6 +73,6 @@ M: Kishore Bodke <kishore.k.bodke@...> F: meta-romley/ SUGARBAY -M: Tom Zanussi <tom.zanussi@...> +M: Nitin A Kamble<nitin.a.kamble@...> F: meta-sugarbay/ diff --git a/meta-chiefriver/README b/meta-chiefriver/README index 438c293..7c47b02 100644 --- a/meta-chiefriver/README +++ b/meta-chiefriver/README @@ -24,6 +24,17 @@ This layer depends on: branch: master +Patches +======= + +Please submit any patches against this BSP to the Yocto mailing list +(yocto@...) and cc: the maintainer: + +Maintainer: Nitin A Kamble <nitin.a.kamble@...> + +Please see the meta-intel/MAINTAINERS file for more details. + + Table of Contents ================= diff --git a/meta-crownbay/README b/meta-crownbay/README index f7aeffa..4bc9f31 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README @@ -32,7 +32,7 @@ Patches Please submit any patches against this BSP to the Yocto mailing list (yocto@...) and cc: the maintainer: -Maintainer: Tom Zanussi <tom.zanussi@...> +Maintainer: Nitin A Kamble <nitin.a.kamble@...> Please see the meta-intel/MAINTAINERS file for more details. diff --git a/meta-emenlow/README b/meta-emenlow/README index 9bef671..3932718 100644 --- a/meta-emenlow/README +++ b/meta-emenlow/README @@ -36,7 +36,7 @@ Patches Please submit any patches against this BSP to the Yocto mailing list (yocto@...) and cc: the maintainer: -Maintainer: Tom Zanussi <tom.zanussi@...> +Maintainer: Nitin A Kamble <nitin.a.kamble@...> Please see the meta-intel/MAINTAINERS file for more details. diff --git a/meta-jasperforest/README b/meta-jasperforest/README index 78852bd..12f84c2 100644 --- a/meta-jasperforest/README +++ b/meta-jasperforest/README @@ -31,7 +31,7 @@ Patches Please submit any patches against this BSP to the Yocto mailing list (yocto@...) and cc: the maintainer: -Maintainer: Tom Zanussi <tom.zanussi@...> +Maintainer: Nitin A Kamble <nitin.a.kamble@...> Please see the meta-intel/MAINTAINERS file for more details. diff --git a/meta-sugarbay/README b/meta-sugarbay/README index 80833c1..c8a99d7 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README @@ -30,7 +30,7 @@ Patches Please submit any patches against this BSP to the Yocto mailing list (yocto@...) and cc: the maintainer: -Maintainer: Tom Zanussi <tom.zanussi@...> +Maintainer: Nitin A Kamble <nitin.a.kamble@...> Please see the meta-intel/MAINTAINERS file for more details. -- 1.7.3.4
|
|
[PATCH 0/5] Misc meta-intel commits
nitin.a.kamble@...
From: Nitin A Kamble <nitin.a.kamble@...>
Various commits here. Thanks, Nitin The following changes since commit 2bd31135bdcdda19dabdf69706d9a38d5872e1fe: crownbay: uprev v3.4 kernel commit ids (2012-10-08 16:09:33 -0500) are available in the git repository at: git://git.yoctoproject.org/meta-intel-contrib nitin/misc http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc Nitin A Kamble (5): xf86-video-intel: Bring 2.20.0 version to match released graphics stack crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri emgd-driver_bin_1.10: drop it as all BSP using EMGD have switched to 1.14 version now fishriver BSP retirement update maintainers of various BSPs MAINTAINERS | 16 +-- .../xorg-driver/emgd-driver-bin_1.10.bb | 93 ---------------- .../xorg-driver/xf86-video-intel_2.20.0.bb | 26 +++++ .../xorg-driver/xorg-driver-common.inc | 33 ++++++ .../xorg-driver/xorg-driver-video.inc | 4 + meta-chiefriver/README | 11 ++ meta-crownbay/README | 2 +- meta-crownbay/conf/machine/crownbay.conf | 2 +- meta-emenlow/README | 2 +- meta-fishriver/COPYING.MIT | 17 --- meta-fishriver/README | 114 -------------------- meta-fishriver/README.sources | 17 --- meta-fishriver/conf/layer.conf | 12 -- meta-fishriver/conf/machine/fishriver.conf | 17 --- .../formfactor/formfactor/fishriver/machconfig | 3 - .../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 - .../xserver-xf86-config/fishriver/xorg.conf | 26 ----- .../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 - .../linux/linux-yocto-rt_3.0.bbappend | 8 -- .../linux/linux-yocto-rt_3.2.bbappend | 8 -- .../recipes-kernel/linux/linux-yocto_3.0.bbappend | 9 -- .../recipes-kernel/linux/linux-yocto_3.2.bbappend | 8 -- .../recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 -- meta-jasperforest/README | 2 +- meta-sugarbay/README | 2 +- 25 files changed, 85 insertions(+), 359 deletions(-) delete mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb create mode 100644 common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-common.inc create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-video.inc delete mode 100644 meta-fishriver/COPYING.MIT delete mode 100644 meta-fishriver/README delete mode 100644 meta-fishriver/README.sources delete mode 100644 meta-fishriver/binary/.gitignore delete mode 100644 meta-fishriver/conf/layer.conf delete mode 100644 meta-fishriver/conf/machine/fishriver.conf delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend -- 1.7.3.4
|
|
[PATCH 4/5] fishriver BSP retirement
nitin.a.kamble@...
From: Nitin A Kamble <nitin.a.kamble@...>
This commit removes fishriver bsp from meta-intel layer. Signed-off-by: Nitin A Kamble <nitin.a.kamble@...> --- MAINTAINERS | 4 - meta-fishriver/COPYING.MIT | 17 --- meta-fishriver/README | 114 -------------------- meta-fishriver/README.sources | 17 --- meta-fishriver/conf/layer.conf | 12 -- meta-fishriver/conf/machine/fishriver.conf | 17 --- .../formfactor/formfactor/fishriver/machconfig | 3 - .../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 - .../xserver-xf86-config/fishriver/xorg.conf | 26 ----- .../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 - .../linux/linux-yocto-rt_3.0.bbappend | 8 -- .../linux/linux-yocto-rt_3.2.bbappend | 8 -- .../recipes-kernel/linux/linux-yocto_3.0.bbappend | 9 -- .../recipes-kernel/linux/linux-yocto_3.2.bbappend | 8 -- .../recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 -- 15 files changed, 0 insertions(+), 255 deletions(-) delete mode 100644 meta-fishriver/COPYING.MIT delete mode 100644 meta-fishriver/README delete mode 100644 meta-fishriver/README.sources delete mode 100644 meta-fishriver/binary/.gitignore delete mode 100644 meta-fishriver/conf/layer.conf delete mode 100644 meta-fishriver/conf/machine/fishriver.conf delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend diff --git a/MAINTAINERS b/MAINTAINERS index 5bcf470..3bf0add 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -56,10 +56,6 @@ EMENLOW M: Tom Zanussi <tom.zanussi@...> F: meta-emenlow/ -FISHRIVER -M: Tom Zanussi <tom.zanussi@...> -F: meta-fishriver/ - FRI2 M: Darren Hart <dvhart@...> F: meta-fri2/ diff --git a/meta-fishriver/COPYING.MIT b/meta-fishriver/COPYING.MIT deleted file mode 100644 index fb950dc..0000000 --- a/meta-fishriver/COPYING.MIT +++ /dev/null @@ -1,17 +0,0 @@ -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in -all copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -THE SOFTWARE. diff --git a/meta-fishriver/README b/meta-fishriver/README deleted file mode 100644 index 1dd0a4c..0000000 --- a/meta-fishriver/README +++ /dev/null @@ -1,114 +0,0 @@ -This README file contains information on building the meta-fishriver -BSP layer, and booting the images contained in the /binary directory. -Please see the corresponding sections below for details. - - -Dependencies -============ - -This layer depends on: - - URI: git://git.openembedded.org/bitbake - branch: master - - URI: git://git.openembedded.org/openembedded-core - layers: meta - branch: master - - URI: git://git.yoctoproject.org/meta-intel - layers: intel - branch: master - - -Patches -======= - -Please submit any patches against this BSP to the Yocto mailing list -(yocto@...) and cc: the maintainer: - -Maintainer: Tom Zanussi <tom.zanussi@...> - -Please see the meta-intel/MAINTAINERS file for more details. - - -Table of Contents -================= - - I. Building the meta-fishriver BSP layer - II. Booting the images in /binary - - -I. Building the meta-fishriver BSP layer -======================================== - -In order to build an image with BSP support for a given release, you -need to download the corresponding BSP tarball from the 'Board Support -Package (BSP) Downloads' page of the Yocto Project website. - -Having done that, and assuming you extracted the BSP tarball contents -at the top-level of your yocto build tree, you can build a fishriver -image by adding the location of the meta-fishriver layer to -bblayers.conf, along with the meta-intel layer itself (to access -common metadata shared between BSPs) e.g.: - - yocto/meta-intel \ - yocto/meta-intel/meta-fishriver \ - -To enable the fishriver layer, add the fishriver MACHINE to local.conf: - - MACHINE ?= "fishriver" - -You should then be able to build a fishriver image as such: - - $ source oe-init-build-env - $ bitbake core-image-sato - -At the end of a successful build, you should have a live image that -you can boot from a USB flash drive (see instructions on how to do -that below, in the section 'Booting the images from /binary'). - -As an alternative to downloading the BSP tarball, you can also work -directly from the meta-intel git repository. For each BSP in the -'meta-intel' repository, there are multiple branches, one -corresponding to each major release starting with 'laverne' (0.90), in -addition to the latest code which tracks the current master (note that -not all BSPs are present in every release). Instead of extracting a -BSP tarball at the top level of your yocto build tree, you can -equivalently check out the appropriate branch from the meta-intel -repository at the same location. - - -II. Booting the images in /binary -================================= - -This BSP contains bootable live images, which can be used to directly -boot Yocto off of a USB flash drive. - -Under Linux, insert a USB flash drive. Assuming the USB flash drive -takes device /dev/sdf, use dd to copy the live image to it. For -example: - -# dd if=core-image-sato-fishriver-20101207053738.hddimg of=/dev/sdf -# sync -# eject /dev/sdf - -This should give you a bootable USB flash device. Insert the device -into a bootable USB socket on the target, and power on. This should -result in a system booted to the Sato graphical desktop. - -If you want a terminal, use the arrows at the top of the UI to move to -different pages of available applications, one of which is named -'Terminal'. Clicking that should give you a root terminal. - -If you want to ssh into the system, you can use the root terminal to -ifconfig the IP address and use that to ssh in. The root password is -empty, so to log in type 'root' for the user name and hit 'Enter' at -the Password prompt: and you should be in. - ----- - -If you find you're getting corrupt images on the USB (it doesn't show -the syslinux boot: prompt, or the boot: prompt contains strange -characters), try doing this first: - -# dd if=/dev/zero of=/dev/sdf bs=1M count=512 diff --git a/meta-fishriver/README.sources b/meta-fishriver/README.sources deleted file mode 100644 index 76180f1..0000000 --- a/meta-fishriver/README.sources +++ /dev/null @@ -1,17 +0,0 @@ -The sources for the packages comprising the images shipped with this -BSP can be found at the following location: - -http://downloads.yoctoproject.org/mirror/sources/ - -The metadata used to generate the images shipped with this BSP, in -addition to the code contained in this BSP, can be found at the -following location: - -http://www.yoctoproject.org/downloads/yocto-1.2/poky-denzil-7.0.tar.bz2 - -The metadata used to generate the images shipped with this BSP, in -addition to the code contained in this BSP, can also be found at the -following locations: - -git://git.yoctoproject.org/poky.git -git://git.yoctoproject.org/meta-intel diff --git a/meta-fishriver/binary/.gitignore b/meta-fishriver/binary/.gitignore deleted file mode 100644 index e69de29..0000000 diff --git a/meta-fishriver/conf/layer.conf b/meta-fishriver/conf/layer.conf deleted file mode 100644 index 61e292b..0000000 --- a/meta-fishriver/conf/layer.conf +++ /dev/null @@ -1,12 +0,0 @@ -# We have a conf and classes directory, add to BBPATH -BBPATH := "${BBPATH}:${LAYERDIR}" - -# We have a recipes directory, add to BBFILES -BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \ - ${LAYERDIR}/recipes-*/*/*.bbappend" - -BBFILE_COLLECTIONS += "fishriver" -BBFILE_PATTERN_fishriver := "^${LAYERDIR}/" -BBFILE_PRIORITY_fishriver = "6" - -LAYERDEPENDS_fishriver = "intel" diff --git a/meta-fishriver/conf/machine/fishriver.conf b/meta-fishriver/conf/machine/fishriver.conf deleted file mode 100644 index ec2e87f..0000000 --- a/meta-fishriver/conf/machine/fishriver.conf +++ /dev/null @@ -1,17 +0,0 @@ -#@TYPE: Machine -#@NAME: fishriver - -#@DESCRIPTION: Machine configuration for Fish River Island systems -# i.e. Z530/E660 + EG20T - -PREFERRED_VERSION_linux-yocto ?= "3.4%" - -require conf/machine/include/tune-atom.inc -require conf/machine/include/ia32-base.inc - -XSERVER ?= "${XSERVER_IA32_BASE} \ - ${XSERVER_IA32_EXT} \ - ${XSERVER_IA32_VESA} \ - " - -APPEND += "video=vesafb vga=0x318" diff --git a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig b/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig deleted file mode 100644 index ffce012..0000000 --- a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig +++ /dev/null @@ -1,3 +0,0 @@ -# Assume a USB mouse and keyboard are connected -HAVE_TOUCHSCREEN=0 -HAVE_KEYBOARD=1 diff --git a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend deleted file mode 100644 index 54da0ff..0000000 --- a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend +++ /dev/null @@ -1,3 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" - -PRINC = "1" diff --git a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf deleted file mode 100644 index da4fc3c..0000000 --- a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf +++ /dev/null @@ -1,26 +0,0 @@ -Section "Device" - Identifier "Generic VESA" - Driver "vesa" -EndSection - -Section "Monitor" - Identifier "Generic Monitor" - Option "DPMS" -EndSection - -Section "Screen" - Identifier "Default Screen" - Device "Generic VESA" - Monitor "Generic Monitor" - DefaultDepth 24 -EndSection - -Section "ServerLayout" - Identifier "Default Layout" - Screen "Default Screen" -EndSection - -Section "ServerFlags" - Option "DontZap" "0" - Option "AutoAddDevices" "False" -EndSection diff --git a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend deleted file mode 100644 index 72d991c..0000000 --- a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend +++ /dev/null @@ -1 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend deleted file mode 100644 index 7a502bd..0000000 --- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend +++ /dev/null @@ -1,8 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" -COMPATIBLE_MACHINE_fishriver = "fishriver" -KMACHINE_fishriver = "fishriver" - -# Update the following to use a different BSP branch or meta SRCREV -#KBRANCH_fishriver = "yocto/standard/preempt-rt/base" -#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX -#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend deleted file mode 100644 index a91a425..0000000 --- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend +++ /dev/null @@ -1,8 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" -COMPATIBLE_MACHINE_fishriver = "fishriver" -KMACHINE_fishriver = "fishriver" - -# Update the following to use a different BSP branch or meta SRCREV -#KBRANCH_fishriver = "standard/preempt-rt/base" -#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX -#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend deleted file mode 100644 index 6ac6ef5..0000000 --- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend +++ /dev/null @@ -1,9 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" - -COMPATIBLE_MACHINE_fishriver = "fishriver" -KMACHINE_fishriver = "fishriver" -KBRANCH_fishriver = "yocto/standard/fishriver" -KERNEL_FEATURES_append_fishriver += " cfg/smp.scc" - -SRCREV_machine_pn-linux-yocto_fishriver ?= "c139592c96722727a9f074515a4061c3820da1a6" -SRCREV_meta_pn-linux-yocto_fishriver ?= "59314a3523e360796419d76d78c6f7d8c5ef2593" diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend deleted file mode 100644 index 9a2f678..0000000 --- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend +++ /dev/null @@ -1,8 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" - -COMPATIBLE_MACHINE_fishriver = "fishriver" -KMACHINE_fishriver = "fishriver" -KBRANCH_fishriver = "standard/default/fishriver" - -SRCREV_machine_pn-linux-yocto_fishriver ?= "969edd015a46eed77d6c3daeffdc299dd06e3397" -SRCREV_meta_pn-linux-yocto_fishriver ?= "5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b" diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend deleted file mode 100644 index c0d04dc..0000000 --- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend +++ /dev/null @@ -1,8 +0,0 @@ -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" - -COMPATIBLE_MACHINE_fishriver = "fishriver" -KMACHINE_fishriver = "fishriver" -KBRANCH_fishriver = "standard/fishriver" - -SRCREV_machine_pn-linux-yocto_fishriver ?= "3fa06aa29078fdb2af431de2d3fdae7d281ba85f" -SRCREV_meta_pn-linux-yocto_fishriver ?= "5bdc655034a58a7147176a8a882d81e2fd51e4b9" -- 1.7.3.4
|
|
[PATCH 3/5] emgd-driver_bin_1.10: drop it as all BSP using EMGD have switched to 1.14 version now
nitin.a.kamble@...
From: Nitin A Kamble <nitin.a.kamble@...>
Signed-off-by: Nitin A Kamble <nitin.a.kamble@...> --- .../xorg-driver/emgd-driver-bin_1.10.bb | 93 -------------------- 1 files changed, 0 insertions(+), 93 deletions(-) delete mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb diff --git a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb deleted file mode 100644 index 6d80bee..0000000 --- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb +++ /dev/null @@ -1,93 +0,0 @@ -SUMMARY = "EMGD 1.10 xserver binaries" -DESCRIPTION = "EMGD 1.10 includes some userspace binaries that use non-free \ -licensing, which are now available via a non-click-through downloadable \ -tarball, and is what this recipe now uses. Since it is a non-free license, \ -this recipe is marked as 'License_emgd-driver-bin_1.10' and you need to add \ -to LICENSE_FLAGS_WHITELIST += \"License_emgd-driver-bin_1.10\" to your \ -local.conf in order to enable it in a build." -LICENSE = "Intel-binary-only" -LICENSE_FLAGS = "license_${PN}_${PV}" -PR = "r1" - -EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License" -EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2" -EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin" - -LIC_FILES_CHKSUM = "file://${WORKDIR}/${EMGD_LIC_DIR}/License.txt;md5=b54f01caaf8483b3cb60c0c40f2bf22d" - -DEPENDS = "rpm-native xz-native" - -SRC_URI = "https://edc.intel.com/App_Shared/Downloads/LIN_EMGD_1_10_RC_2209.tgz" - -SRC_URI[md5sum] = "e4a38d9efa0b086ae21b68145c4db4e9" -SRC_URI[sha256sum] = "acea5f0f93a31553553428623c007d7ed0c604cf715fd87dfe075751da4be548" - -# These are closed binaries generated elsewhere so don't check ldflags -INSANE_SKIP_${PN} = "ldflags" -# Inhibit warnings about files being stripped, we can't do anything about it. -INHIBIT_PACKAGE_DEBUG_SPLIT = "1" - -FILES_${PN} += "${libdir}/dri ${libdir}/gstreamer-0.10 ${libdir}/xorg/modules/drivers" -FILES_${PN}-dbg += "${libdir}/xorg/modules/drivers/.debug ${libdir}/dri/.debug" - -S = "${WORKDIR}/${EMGD_RPM_DIR}" - -do_install () { - # A gstreamer VA buffer library - rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-vabuffer*.rpm | cpio -id - - # MIX Common contains common classes, datatype, header files used by other MIX components - rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixcommon*.rpm | cpio -id - - # MIX Video Bitstream Parser is an user library interface for various video format bitstream parsing - rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvbp*.rpm | cpio -id - - # MIX Video is an user library interface for various video codecs available on the platform. - rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvideo*.rpm | cpio -id - - install -d -m 0755 ${D}${libdir}/gstreamer-0.10 - install -m 0755 ${S}/usr/lib/* ${D}${libdir}/ - - # A gstreamer plugin that uses MIX Video for hardware accelerated video decoding and rendering. - rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-mixvideo*.rpm | cpio -id - - # A collection of gstreamer plugins that uses VA libraries for hardware accelerated video rendering and text overlay. - rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-va*.rpm | cpio -id - - install -m 0755 ${S}/usr/lib/gstreamer-0.10/* ${D}${libdir}/gstreamer-0.10/ - - # EMGD runtime graphics libraries - rpm2cpio ${S}/emgd-bin*.rpm | xz -d | cpio -id - - install -d -m 0755 ${D}${libdir}/dri - install -d -m 0755 ${D}${libdir}/xorg/modules/drivers - install -d -m 0755 ${D}${sysconfdir} - install -d -m 0755 ${D}${mandir}/man4 - install -m 0755 ${S}/usr/lib/*.so.* ${D}${libdir}/ - install -m 0755 ${S}/usr/lib/dri/* ${D}${libdir}/dri/ - install -m 0755 ${S}/usr/lib/xorg/modules/drivers/* ${D}${libdir}/xorg/modules/drivers/ - install -m 0755 ${S}/etc/* ${D}${sysconfdir}/ - install -m 0755 ${S}/usr/share/man/man4/* ${D}${mandir}/man4/ - - # Khronos development headers needed for EGL, OpenGL-ES, and OpenVG development - rpm2cpio ${S}/emgd-devel*.rpm | xz -d | cpio -id - - install -d -m 0755 ${D}${includedir}/EGL - install -m 0755 ${S}/usr/include/EGL/*.h ${D}${includedir}/EGL/ - install -d -m 0755 ${D}${includedir}/GLES - install -m 0755 ${S}/usr/include/GLES/*.h ${D}${includedir}/GLES/ - install -d -m 0755 ${D}${includedir}/GLES2 - install -m 0755 ${S}/usr/include/GLES2/*.h ${D}${includedir}/GLES2/ - install -d -m 0755 ${D}${includedir}/KHR - install -m 0755 ${S}/usr/include/KHR/*.h ${D}${includedir}/KHR/ - install -d -m 0755 ${D}${includedir}/VG - install -m 0755 ${S}/usr/include/VG/*.h ${D}${includedir}/VG/ - - ln -sf libEGL.so.1 ${D}${libdir}/libEGL.so - ln -sf libGLES_CM.so.1 ${D}${libdir}/libGLES_CM.so - ln -sf libGLESv2.so.2 ${D}${libdir}/libGLESv2.so - ln -sf libOpenVG.so.1 ${D}${libdir}/libOpenVG.so - ln -sf libOpenVGU.so.1 ${D}${libdir}/libOpenVGU.so -} - -LEAD_SONAME = "libEGL.so" -- 1.7.3.4
|
|
[PATCH 2/5] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri
nitin.a.kamble@...
From: Nitin A Kamble <nitin.a.kamble@...>
This commit fixes the bug: [YOCTO #3328] Signed-off-by: Nitin A Kamble <nitin.a.kamble@...> --- meta-crownbay/conf/machine/crownbay.conf | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf index c18fa1d..72431de 100644 --- a/meta-crownbay/conf/machine/crownbay.conf +++ b/meta-crownbay/conf/machine/crownbay.conf @@ -18,7 +18,7 @@ XSERVER ?= "${XSERVER_IA32_BASE} \ " PREFERRED_VERSION_xserver-xorg ?= "1.9.3" -PREFERRED_VERSION_mesa-dri ?= "7.11" +PREFERRED_VERSION_mesa-dri ?= "8.0.4" PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0" APPEND += "video=vesafb vga=0x318 vmalloc=256MB" -- 1.7.3.4
|
|
[PATCH 1/5] xf86-video-intel: Bring 2.20.0 version to match released graphics stack
nitin.a.kamble@...
From: Nitin A Kamble <nitin.a.kamble@...>
The Intel Linux graphics stack version 12.07 released on 2012-07-24 requires version 2.20.0 as seen here: http://intellinuxgraphics.org/2012.07.html Currently oecore has 2.19.0 version. So get this 2.20.0 version in meta-intel layer to be used by sugarbay and other BSPs using the Intel graphics stack. Signed-off-by: Nitin A Kamble <nitin.a.kamble@...> --- .../xorg-driver/xf86-video-intel_2.20.0.bb | 26 +++++++++++++++ .../xorg-driver/xorg-driver-common.inc | 33 ++++++++++++++++++++ .../xorg-driver/xorg-driver-video.inc | 4 ++ 3 files changed, 63 insertions(+), 0 deletions(-) create mode 100644 common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-common.inc create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-video.inc diff --git a/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb b/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb new file mode 100644 index 0000000..a7bf45a --- /dev/null +++ b/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb @@ -0,0 +1,26 @@ +require xorg-driver-video.inc + +SUMMARY = "X.Org X server -- Intel integrated graphics chipsets driver" + +DESCRIPTION = "intel is an Xorg driver for Intel integrated graphics \ +chipsets. The driver supports depths 8, 15, 16 and 24. On some chipsets, \ +the driver supports hardware accelerated 3D via the Direct Rendering \ +Infrastructure (DRI)." + +LIC_FILES_CHKSUM = "file://COPYING;md5=8730ad58d11c7bbad9a7066d69f7808e" + +PR = "${INC_PR}.0" + +DEPENDS += "virtual/libx11 drm xf86driproto glproto \ + virtual/libgl xineramaproto xf86driproto libpciaccess" + + +EXTRA_OECONF += "--disable-xvmc" + +# --enable-kms-only option is required by ROOTLESS_X +EXTRA_OECONF += '${@base_conditional( "ROOTLESS_X", "1", " --enable-kms-only", "", d )}' + +COMPATIBLE_HOST = '(i.86|x86_64).*-linux' + +SRC_URI[md5sum] = "070bb866b05a16366bd9bb844c9b91aa" +SRC_URI[sha256sum] = "21949297220ceda32bba430f778c6409002079dc717c7190dbd1062ab4a56783" diff --git a/common/recipes-graphics/xorg-driver/xorg-driver-common.inc b/common/recipes-graphics/xorg-driver/xorg-driver-common.inc new file mode 100644 index 0000000..1ed2742 --- /dev/null +++ b/common/recipes-graphics/xorg-driver/xorg-driver-common.inc @@ -0,0 +1,33 @@ +DESCRIPTION = "X driver" +HOMEPAGE = "http://www.x.org" +BUGTRACKER = "https://bugs.freedesktop.org" +SECTION = "x11/drivers" +LICENSE = "MIT-X" + +PE = "2" +INC_PR = "r0" + +DEPENDS = "virtual/xserver xproto randrproto util-macros" + +SRC_URI = "${XORG_MIRROR}/individual/driver/${BPN}-${PV}.tar.bz2" + +S = "${WORKDIR}/${BPN}-${PV}" + +FILES_${PN} += " ${libdir}/xorg/modules/drivers/*.so" +FILES_${PN}-dbg += " ${libdir}/xorg/modules/drivers/.debug" + +inherit autotools pkgconfig + +# AC_CHECK_FILE doesn't work when cross compiling, so we create a replacement +# macro that simply assumes the test succeeds. +do_configure_prepend () { + echo 'AC_DEFUN(CC_AC_CHECK_FILE, $2)' > configure.ac.new + sed 's/AC_CHECK_FILE/CC_AC_CHECK_FILE/g' configure.ac >> configure.ac.new + mv configure.ac.new configure.ac +} + +# FIXME: We don't want to include the libtool archives (*.la) from modules +# directory, as they serve no useful purpose. Upstream should fix Makefile.am +do_install_append() { + find ${D}${libdir}/xorg/modules -regex ".*\.la$" | xargs rm -f -- +} diff --git a/common/recipes-graphics/xorg-driver/xorg-driver-video.inc b/common/recipes-graphics/xorg-driver/xorg-driver-video.inc new file mode 100644 index 0000000..57c80d1 --- /dev/null +++ b/common/recipes-graphics/xorg-driver/xorg-driver-video.inc @@ -0,0 +1,4 @@ +include xorg-driver-common.inc + +DEPENDS =+ "renderproto videoproto xextproto fontsproto" + -- 1.7.3.4
|
|
Re: CyaSSL Yocto Recipe
Chris Conlon <chris@...>
On Sep 6, 2012, at 4:53 PM, Richard Purdie wrote:
This looks like an interesting piece of software and a quick readAs suggested, we have created a yaSSL layer (meta-yassl) which includes a recipe for the CyaSSL embedded SSL library. The layer can be found on GitHub, here: https://github.com/cconlon/meta-yassl Any comments or suggestions on improving the layer would be greatly appreciated. Going forward from here, what would make the most sense as a next step? Thanks, Chris Conlon www.yassl.com chris@... Skype: chris_conlon_07 +1 406 209 0601
|
|
building under Centos 6.3
Jim Abernathy
Just an FYI, following the Getting Started Guide for Centos prerequisites, I found one that was not listed that I needed: "chrpath".
|
|
Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel
Chris Tapp
On 9 Oct 2012, at 14:40, James Abernathy wrote:
Interesting - that's the same board as I'm using. It would be worth seeing what happens. I've had a look at the bbappend for 3.2 that Kishore posted and compared it with the standard one for 3.0. I think it 'just' needs a new meta data branch before I can try a build with pvr. I guess this will need to be a new branch and not an existing one?
Chris Tapp
|
|
Re: Newbie looking for a Recipe Box for AM1707 aka Texas Instruments TMDXEVM1707
Denys Dmytriyenko
On Tue, Sep 25, 2012 at 09:27:22AM -0400, Wesley J. Miller wrote:
The subject pretty much says it all.Hi, Sorry for the delay. You can start with the MACHINE=am180x-evm from meta-ti[1], as it's close enough and from basic BSP perspective should be the same. [1] http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ -- Denys
|
|
Re: [RFCv2 0/3] [eclipse-poky] Cheat sheet for hello world project
Zhang, Jessica
Hi Atanas,
toggle quoted messageShow quoted text
The patch set is merged to eclipse-poky master, thanks for the contribution. Cheers, Jessica
-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Atanas Gegov Sent: Thursday, October 04, 2012 7:54 AM To: yocto@... Subject: [yocto] [RFCv2 0/3] [eclipse-poky] Cheat sheet for hello world project From: Atanas Gegov <atanas.gegov@...> Hi Jessica, Please excuse my late reaction, but I was on vacation in August and had some high-priority organisational issues at work in Septmeber. I improved the cheat sheet accroding to your feedback. I used conditional subitems to make it both fit for the "Hello World C++ Autotools Project" and the "Hello World ANSI C Project". The user can now choose its preferred programming language and the cheat sheet adapts itself accordingly. I also took into account that the SDK is now relocatable. The patches apply both on the "master" and on the "master-indigo" branches. Cheers, Atanas Atanas Gegov (3): plugins/sdk.ide.doc.user: Added plugin for ide specific user help feature/sdk: Added user doc plugin plugins/sdk.ide.doc.user: Added cheat sheet for hello world project features/org.yocto.sdk/feature.xml | 8 + plugins/org.yocto.sdk.ide.doc.user/.classpath | 6 + plugins/org.yocto.sdk.ide.doc.user/.project | 28 +++ .../.settings/org.eclipse.jdt.core.prefs | 8 + .../META-INF/MANIFEST.MF | 8 + .../OSGI-INF/l10n/bundle.properties | 7 + .../org.yocto.sdk.ide.doc.user/build.properties | 6 + .../cheatsheets/createNewHelloWorldProject.xml | 222 ++++++++++++++++++++ plugins/org.yocto.sdk.ide.doc.user/plugin.xml | 13 ++ 9 files changed, 306 insertions(+), 0 deletions(-) create mode 100644 plugins/org.yocto.sdk.ide.doc.user/.classpath create mode 100644 plugins/org.yocto.sdk.ide.doc.user/.project create mode 100644 plugins/org.yocto.sdk.ide.doc.user/.settings/org.eclipse.jdt.core.prefs create mode 100644 plugins/org.yocto.sdk.ide.doc.user/META-INF/MANIFEST.MF create mode 100644 plugins/org.yocto.sdk.ide.doc.user/OSGI-INF/l10n/bundle.properties create mode 100644 plugins/org.yocto.sdk.ide.doc.user/build.properties create mode 100644 plugins/org.yocto.sdk.ide.doc.user/cheatsheets/createNewHelloWorldProject.xml create mode 100644 plugins/org.yocto.sdk.ide.doc.user/plugin.xml -- 1.7.5.4 _______________________________________________ yocto mailing list yocto@... https://lists.yoctoproject.org/listinfo/yocto
|
|
Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel
Jim Abernathy
On Mon, Oct 8, 2012 at 12:28 PM, Saxena, Rahul <rahul.saxena@...> wrote:
It may not solve the 3.0 problem for CDV and Yocto, but I noticed that Ubuntu 12.04.1 with the 3.2 kernel supports the PVR driver on it's 3.2.0 kernel. I've only tested it successfully on an All-In-One with LVDS off of an eDP to LVDS converter used on the DN2800MT motherboard.
Jim A
|
|
Re: The BitBake equivalent of "Hello, World!"
Rudolf Streif <rudolf.streif@...>
The T variable points to a directory were Bitbake places temporary files when building a particular package. It is typically set to
toggle quoted messageShow quoted text
T = ${WORKDIR}/temp WORKDIR is the directory into which Bitbake unpacks and builds a package. The default bitbake.conf file sets this variable.
T is not to be confused with TMPDIR which points to the root of the directory tree where Bitbake puts the output of an entire build. :rjs
On Mon, Oct 8, 2012 at 5:30 PM, Patrick Turley <PatrickTurley@...> wrote:
|
|
Re: The BitBake equivalent of "Hello, World!"
Patrick Turley <PatrickTurley@...>
I am continuing my work on creating a "Hello, World!" BitBake project. Because of the excellent help I got before, things have gone reasonably well, but I'm again running into something I don't know how to fix.
As before, the entire contents of my very small project appear at the end of this message. Here's what works fine:
$ ../BitBake/bin/bitbake-layers show-layers
Parsing recipes..done.
layer path priority
==========================================================
LayerA /home/pturley/Workspace/Hello/LayerA 1
$ ../BitBake/bin/bitbake-layers show-recipes
Parsing recipes..done.
=== Available recipes: ===
a:
LayerA 1
When I tried this:
../BitBake/bin/bitbake -c listtasks a
I got a Python stack trace that ended here:
File "../BitBake/lib/bb/runqueue.py", line 902, in RunQueue.check_stamp_task(task=0, taskname='do_listtasks', recurse=False):
# If the stamp is missing its not current
> if not os.access(stampfile, os.F_OK):
logger.debug(2, "Stampfile %s not available", stampfile)
TypeError: coercing to Unicode: need string or buffer, NoneType found
This code isn't expecting the "stampfile" variable to be "None" (which it is), so it freaks out. I made a very simple fix to get past the
problem:
if not stampfile or not os.access(stampfile, os.F_OK):
That made a dramatic difference, and enabled me to get this far:
$ ../BitBake/bin/bitbake -c listtasks a
Loading cache: 100% |###############################################################| ETA: 00:00:00
Loaded 2 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 1 (ID: 0, /home/pturley/Workspace/Hello/LayerA/a.bb, do_listtasks)
ERROR: T variable not set, unable to build
ERROR: Task 0 (/home/pturley/Workspace/Hello/LayerA/a.bb, do_listtasks) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/pturley/Workspace/Hello/LayerA/a.bb, do_listtasks
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
$ ../BitBake/bin/bitbake a
Loading cache: 100% |###############################################################| ETA: 00:00:00
Loaded 2 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 1 (ID: 0, /home/pturley/Workspace/Hello/LayerA/a.bb, do_build)
ERROR: T variable not set, unable to build
ERROR: Task 0 (/home/pturley/Workspace/Hello/LayerA/a.bb, do_build) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/pturley/Workspace/Hello/LayerA/a.bb, do_build
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
As you can see, BitBake is expecting the "T" variable to be set. I don't think I've ever seen this variable -- so I don't know what it's for or what I should change.
Can anyone offer a hint?
------------------------------------------------------------
├── build
│ │
│ ├── classes
│ │ │
│ │ └── base.bbclass
│ │
│ │ +-----------------------------------------------
│ │ | addtask listtasks
│ │ |
│ │ | do_listtasks[nostamp] = "1"
│ │ |
│ │ | python do_listtasks() {
│ │ | import sys
│ │ | # emit variables and shell functions
│ │ | #bb.data.emit_env(sys.__stdout__, d)
│ │ | # emit the metadata which isnt valid shell
│ │ | for e in d.keys():
│ │ | if d.getVarFlag(e, 'task'):
│ │ | bb.plain("%s" % e)
│ │ | }
│ │ |
│ │ | addtask build
│ │ |
│ │ | do_build() {
│ │ | echo "Hello"
│ │ | }
│ │ +-----------------------------------------------
│ │
│ └── conf
│ │
│ ├── bblayers.conf
│ │
│ │ +-----------------------------------------------
│ │ | BBLAYERS ?= " \
│ │ | /home/pturley/Workspace/Hello/LayerA \
│ │ | "
│ │ +-----------------------------------------------
│ │
│ └── bitbake.conf
│
│ +-----------------------------------------------
│ | CACHE = "${TOPDIR}/cache"
│ +-----------------------------------------------
│
├── LayerA
│ │
│ ├── a.bb
│ │
│ │ +-----------------------------------------------
│ │ | DESCRIPTION = "Layer A Main Recipe"
│ │ | PN = 'a'
│ │ | PV = '1'
│ │ +-----------------------------------------------
│ │
│ └── conf
│ │
│ └── layer.conf
│
│ +-----------------------------------------------
│ | BBPATH .= ":${LAYERDIR}"
│ |
│ | BBFILES += "${LAYERDIR}/*.bb"
│ |
│ | BBFILE_COLLECTIONS += "A"
│ | BBFILE_PATTERN_A := "^${LAYERDIR}/"
│ +-----------------------------------------------
│
└── BitBake
The BitBake directory origin is:
I have the 1.15.2 tag checked out, which is what
Yocto denzil uses.
|
|
Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel
Chris Tapp
On 8 Oct 2012, at 22:03, Chris Tapp wrote:
On 8 Oct 2012, at 21:30, Bodke, Kishore K wrote:Got it - I should have realised this would need to be using the latest denzil head. I've now got a working unionfs. A few minor kernel configuration issues to sort (e.g. Apple HID for my keyboard) and I'll be there. Thanks again for the help. One final question - does lack of PVR mean I won't have a framebuffer device? I've got the vesa one, but I can't use video=... in the kernel command line. Not a show stopper by any means, but the video= stanza is much easier for general users to modify. Chris TappAdd these below lines to meta-cedartrail/conf/machine/cedartrail-nopvr.confOf course, and that's the bit I understand ;-) opensource@... www.keylevel.com
|
|
Re: [PATCHv3 0/1] meta-intel misc commits
Tom Zanussi <tom.zanussi@...>
On Fri, 2012-10-05 at 19:17 -0700, nitin.a.kamble@... wrote:
From: Nitin A Kamble <nitin.a.kamble@...>Pulled into meta-intel/master. Thanks, Tom
|
|
Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel
Chris Tapp
On 8 Oct 2012, at 21:30, Bodke, Kishore K wrote:
< snip ... > Thanks for the really fast response on this :-) For denzil, try with this by creating a new file in meta-cedartrail/recipes-kernel/linux/linux-yocto_3.2.bbappend.I had to add 'bareclone=1' to this to get it to run. COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"I think it's nearly there, but I get a failure when validating the branch: NOTE: package linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1: task do_validate_branches: Started ERROR: Function failed: do_validate_branches (see /media/SSD-RAID/build-denzil-git-sjs-cedartrail/tmp/work/cedartrail_nopvr-sjs-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1/temp/log.do_validate_branches.25866 for further information) ERROR: Logfile of failure stored in: /media/SSD-RAID/build-denzil-git-sjs-cedartrail/tmp/work/cedartrail_nopvr-sjs-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1/temp/log.do_validate_branches.25866 Log data follows: | ERROR: Function failed: do_validate_branches (see /media/SSD-RAID/build-denzil-git-sjs-cedartrail/tmp/work/cedartrail_nopvr-sjs-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1/temp/log.do_validate_branches.25866 for further information) NOTE: package linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1: task do_validate_branches: Failed ERROR: Task 0 (/media/SSD-RAID/poky-git/meta/recipes-kernel/linux/linux-yocto_3.2.bb, do_validate_branches) failed with exit code '1' Add these below lines to meta-cedartrail/conf/machine/cedartrail-nopvr.confOf course, and that's the bit I understand ;-) ThanksChris Tapp opensource@... www.keylevel.com
|
|
Agenda: Yocto Project Technical Team Meeting - Tuesday, October 09, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Liu, Song <song.liu@...>
Agenda:
* Opens collection - 5 min (Song) * Yocto 1.3 status - 10 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status - Medium+ bugs review: https://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&list_id=16013&priority=Medium%2B&query_format=advanced&target_milestone=1.3&target_milestone=1.3%20M1&target_milestone=1.3%20M2&target_milestone=1.3%20M3&target_milestone=1.3%20M4&target_milestone=1.3%20M5&target_milestone=1.3.1&target_milestone=1.3.2&order=assigned_to%20DESC%2Cpriority%2Cbug_status%20DESC%2Cbug_id&query_based_on= * Yocto 1.4 feature open discussion - 10 min (team) https://wiki.yoctoproject.org/wiki/Yocto_1.4_Features * SWAT team rotation: Saul * Opens - 10 min * Team sharing - 20 min -----Original Appointment----- We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference details Conference name: Yocto Technical Team Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time Participants: 30 Duration: 60 minutes Participant passcode: 76994298 Dial-in number: 1.972.995.7777 US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x76994298# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): From office dial 8-9957777 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): From office dial 8-9957777 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): From office dial 8-9957777 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): From IP phone dial 8-9957777 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) From TI Campus use 89957777 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: From TI Campus use 8 995 7777 Outside TI use 03 4331 3777 Malaysia: From IP phone dial 2643799 From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: From Baguio City use 4471177 From Metro Manila area use 8702477 Singapore: From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: From IP phone dial 5606998 From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: From IP phone dial 1363 From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01604 663003 US: 972 995 7777 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 26, 2012 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT
|
|