Re: [yocto] Change in override behavior?
On Tue, May 24, 2016 at 5:31 AM, Richard Purdie
wrote:
> On Fri, 2016-04-29 at 22:09 +1200, Paul Eggleton wrote:
>> On Fri, 29 Apr 2016 12:00:58 Gary Thomas wrote:
>> > On 2016-04-29 11:51, Paul Eggleton wrote:
>> > > On Fri, 29 Apr 2016 09:24:23 Gary Thomas wrote:
>> > > > On 2016-04-29 09:16, Paul Eggleton wrote:
>> > > > Indeed, my machine names do have an upper case letter in them.
>> > > > Any suggestions for how to handle this (short of renaming
>> > > > everything
>> > > > which
>> > > > would be a HUGE chore)?
>> > >
>> > > It's no longer supported I'm afraid, BitBake's datastore is now
>> > > coded to
>> > > expect lowercase for all override values. You say it's a huge
>> > > chore but
>> > > surely a grep -l | xargs -n1 sed -i would do it?
>> >
>> > If I were to rename my target (MACHINE), I'd then have to go
>> > through
>> > and rename all of the directories in the recipes that hold machine
>> > customizations and there are quite a few of those. Similarly I'd
>> > have to rework all the recipes that use the old names (with upper
>> > case
>> > letters) to the new ones. Not impossible, but quite a lot of work.
>>
>> That is unfortunate, but again should be pretty easy to automate
>> (assuming
>> they are local of course and not proliferated across many users'
>> build
>> machines).
>>
>> > Short of actually renaming the target machines, I could add an
>> > additional
>> > override (in .conf) that is lowercase only and update just
>> > the
>> > recipes to use that instead.
>> >
>> > By experimentation, I have found that XYZ_append_ seems to
>> > do
>> > the correct thing, even when has upper case letters.
>> > Maybe this
>> > is an oversight that will be fixed?
>>
>> I'm not sure - Richard?
>
> Sorry for the delay in getting to this. It does sound like there is a
> codepath in bitbake which is still recognising variables with mixed
> case. I took a quick look and think this change appears to address it:
>
> diff --git a/bitbake/lib/bb/data_smart.py b/bitbake/lib/bb/data_smart.py
> index 25c412c..ec6709f 100644
> --- a/bitbake/lib/bb/data_smart.py
> +++ b/bitbake/lib/bb/data_smart.py
> @@ -39,7 +39,7 @@ from bb.COW import COWDictBase
> logger = logging.getLogger("BitBake.Data")
>
> __setvar_keyword__ = ["_append", "_prepend", "_remove"]
> -__setvar_regexp__ =
> re.compile('(?P.*?)(?P_append|_prepend|_remove)(_(?P.*))?$')
> +__setvar_regexp__ =
> re.compile('(?P.*?)(?P_append|_prepend|_remove)(_(?P[^A-Z]*))?$')
> __expand_var_regexp__ = re.compile(r"\${[^{}@\n\t :]+}")
> __expand_python_regexp__ = re.compile(r"\${@.+?}")
What about over-rides which contain only numbers?
It doesn't look like this change is going to filter them out, but they
haven't worked as regular over-rides since:
http://git.openembedded.org/bitbake/commit/?id=c9b9443faa76ee7366b1400a56f826f3f9dec1be
(My personal preference for resolving that inconsistency would be to
re-enable and officially support over-rides containing only numbers).
>
> Cheers,
>
> Richard
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build available for QA
-e A build identified as needing QA has finished on the autobuilder. This build is located at: http://autobuilder.yoctoproject.org/pub/nightly/20160602-1 Build hash information: meta-qt4 : 8b346c465a5efb280f8d0d23f8660f68bf9af59f meta-intel : 9bce6bdccf8ed3d3ae1cc2ae6f1f43c864a4ac34 meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae meta-qt3 : 7d958b928a4a38a186746fabbc0d8169dd8bb3a6 poky : 3a763398272975eee6189209f5b741d7a806376e This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV
On Thu, 2 Jun 2016 10:59:37 +0300
Ionel Badisor wrote:
> On 06/01/2016 08:55 PM, Paul Barker wrote:
> > On Tue, 31 May 2016 10:39:03 +0300
> > Khem Raj wrote:
> >
> >> On May 30, 2016 3:15 PM, "Paul Barker"
> >> wrote:
> >>>
> >>>
> >>> I'm trying to build from a source archive instead of a git
> >>> repository (to avoid a ~1.3GB git clone operation) so the use of
> >>> ${SRCPV} is causing me trouble.
> >>>
> >>
> >> Can you override the whole PV
> >
> > I've given this another look and I can get the recipe to parse if I
> > require linux-raspberrypi.inc before setting PV instead of
> > afterwards. However do_kernel_configme then gets confused looking
> > for a "standard/raspberrypi" configuration. It only works if I
> > modify linux-raspberrypi.inc as per my patch and set PV before
> > requiring that include file.
> >
> > I'm starting to think that I might be doing something wrong here -
> > is there a supported way to build a kernel from an archive instead
> > of a git repository within OE?
> >
> > Thanks,
> > Paul Barker
> >
> Are you trying to avoid repeated cloning operation to save bandwith
> and time or you are trying to save disk space?
I'm trying to reduce "time to first build" on a new build machine as
well as the amount of space/bandwidth needed to mirror downloaded
files.
Instead of setting PV in each recipe I could just duplicate
linux-raspberrypi.inc into my own layer with the change I need. That's
probably the simplest approach for now, I'll just have to keep my eye
on meta-raspberrypi going forward for any changes to
linux-raspberrypi.inc which I'd need to incorporate.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Enable chroot for nativesdk
Hi, Currently, nativesdk doesn't support "chroot". It would be great to enable it for packages support at least. This will allow us to install packages directly into our sdk, try them and eventually add to Yocto if needed. Here might be valid steps to achive this: 1) Add coreutils to nativesdk: TOOLCHAIN_HOST_TASK += nativesdk-coreutils 2) Fix packagemanager support for chrooted nativesdk 1) Create unique symlink to dynamic loader located in nativesdk: Add something like this to POPULATE_SDK_POST_HOST_COMMAND ln -s ld-linux-x86-64.so.2 ld-yocto-nativesdk-x86-64.so.2 and ln -s /opt/poky/1.8/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2 /lib/ld-yocto-nativesdk-x86-64.so.2 2) patch binaries in nativesdk to set new dynamic loader patchelf --set-interpreter /lib/ld-yocto-nativesdk-x86-64.so.2 3) patch binaries in nativesdk to add RPATH: patchelf --set-rpath /opt/poky/1.8/sysroots/x86_64-pokysdk-linux/usr/lib:/opt/poky/1.8/sysroots/x86_64-pokysdk-linux/lib:/lib:/usr/lib Thanks, Oleksandr Poznyak! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky master issue with kernel and gcc version
On 2016-06-02 12:33 PM, Eystein Måløy Stenberg wrote: On 01/06/16 19:53, Bruce Ashfield wrote: On 2016-06-01 10:48 PM, Eystein Måløy Stenberg wrote: Hi, I am trying to build a vexpress-qemu machine targe from poky's master branch, but I get this error compiling the kernel: | /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/compiler-gcc.h:121:30: fatal error: linux/compiler-gcc6.h: No such file or directory Apparently it is picking gcc 6.1 and kernel 4.1.24, which do not play well together. The best approach is probably to use kernel 4.2 or newer. Is there a bug filed for this? I would think this is affecting quite a lot of people as I am not doing any special configuration for my build. We've already fixed all the gcc6.x builds for the supported machines in linux-yocto 4.1/4.4. What kernel tree is that building ? upstream ? linux-yocto ? And if linux-yocto, what branch ? It is building linux-yocto 4.1. I have attached the compilation log, in case that helps. What I am doing is simply building a vexpress-qemu machine with poky's master, so it should be quite straightforward to reproduce. In particular, I am following our projects guide for creating a Mender build at https://github.com/mendersoftware/meta-mender/blob/master/README.md, but I don't think it reaches the Mender-specific layers. Thanks for the help and let me know if there's anything else you need. I'm only validating the oe-core qemu* and yocto reference BSPs. My hands are full with them at the moment. So setting up to build with that config isn't something I can do at the moment. But I can assure you that qemuarm, and the beaglebone have both been built and booted with gcc6.x, so the relevant patches are present. qemuarm login: root root@qemuarm:~# uname -a Linux qemuarm 4.1.24-yocto-standard #1 PREEMPT Thu May 26 13:35:31 EDT 2016 armv5tejl GNU/Linux root@qemuarm:~# cat /proc/version Linux version 4.1.24-yocto-standard (bruce@yow-bashfiel-d4) (gcc version 6.1.1 20160511 (GCC) ) #1 PREEMPT Thu May 26 13:35:31 EDT 2016 Bruce Bruce Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Error building python-imaging_1.1.7.bb
Hello Am new to yocto and am trying to build an image for a Gumstix Pepper board and use ROS. However always get to the point with python-imaging_1.1.7.bb failing do_package_qa. HAve tried just doing the following - bitbake python-imaging But still have the same failure - Build Configuration: BB_VERSION= "1.26.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "pepper" DISTRO= "poky" DISTRO_VERSION= "1.8" TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa8" TARGET_FPU= "vfp-neon" meta meta-yocto= "(nobranch):83aa565d93aacae484976562ef1ae8dbbb6b2bc0" meta-gnome meta-oe meta-xfce meta-systemd meta-networking meta-multimedia meta-python = "(nobranch):10d3c8f85280a0bf867a8e4f84bcda81c290d28e" meta-gumstix = "(nobranch):8ea631d8ef26cb13102dac0910be52674cb7b395" meta-gumstix-extras = "(nobranch):15cfa9fcff75d3d95f66cfa190e1b604ff5ea4f6" meta-ros = "(nobranch):d465a23c0a96e651419d46b29ab7c0c3663da314" meta-ti = "(nobranch):03cb3ff15f3b8535ca409ce682f44ec1b81da0c3" meta-java = "(nobranch):66c97ae7461f4c1a13917131787bb76dc34e6b6f" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: QA Issue: python-imaging: The compile log indicates that host include and/or library paths were used. Please check the log '/home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_compile' for more information. [compile-host-path] ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa ERROR: Logfile of failure stored in: /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_package_qa.11102 ERROR: Task 9 (/home/michael/yocto/poky/meta/recipes-devtools/python/ python-imaging_1.1.7.bb, do_package_qa) failed with exit code '1' NOTE: Tasks Summary: Attempted 695 tasks of which 0 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/michael/yocto/poky/meta/recipes-devtools/python/ python-imaging_1.1.7.bb, do_package_qa Summary: There were 3 ERROR messages shown, returning a non-zero exit code. DEBUG: Executing python function sstate_task_prefunc DEBUG: Python function sstate_task_prefunc finished DEBUG: Executing python function do_package_qa NOTE: DO PACKAGE QA DEBUG: Executing python function read_subpackage_metadata DEBUG: Python function read_subpackage_metadata finished ERROR: QA Issue: python-imaging: The compile log indicates that host include and/or library paths were used. Please check the log '/home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_compile' for more information. [compile-host-path] NOTE: Checking Package: python-imaging-staticdev NOTE: Checking Package: python-imaging-dev NOTE: Checking Package: python-imaging-dbg NOTE: arm-poky-linux-gnueabi-objdump -p /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging-dbg/usr/lib/python2.7/site-packages/PIL/.debug/_imaging.so NOTE: arm-poky-linux-gnueabi-objdump -p /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging-dbg/usr/lib/python2.7/site-packages/PIL/.debug/_imagingmath.so NOTE: arm-poky-linux-gnueabi-objdump -p /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging-dbg/usr/lib/python2.7/site-packages/PIL/.debug/_imagingft.so NOTE: Checking Package: python-imaging-doc NOTE: Checking Package: python-imaging NOTE: arm-poky-linux-gnueabi-objdump -p /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging/usr/lib/python2.7/site-packages/PIL/_imaging.so NOTE: arm-poky-linux-gnueabi-objdump -p /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging/usr/lib/python2.7/site-packages/PIL/_imagingmath.so NOTE: arm-poky-linux-gnueabi-objdump -p /home/michael/yocto/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/packages-split/python-imaging/usr/lib/python2.7/site-packages/PIL/_imagingft.so ERROR: QA run found fatal errors. Please consider fixing them. DEBUG: Python function do_package_qa finished ERROR: Function failed: do_package_qa Any help would be much grateful and please let me know if I should post somewhere else. Thank you all. Cheers, Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky master issue with kernel and gcc version
On 01/06/16 19:53, Bruce Ashfield wrote: On 2016-06-01 10:48 PM, Eystein Måløy Stenberg wrote: Hi, I am trying to build a vexpress-qemu machine targe from poky's master branch, but I get this error compiling the kernel: | /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/compiler-gcc.h:121:30: fatal error: linux/compiler-gcc6.h: No such file or directory Apparently it is picking gcc 6.1 and kernel 4.1.24, which do not play well together. The best approach is probably to use kernel 4.2 or newer. Is there a bug filed for this? I would think this is affecting quite a lot of people as I am not doing any special configuration for my build. We've already fixed all the gcc6.x builds for the supported machines in linux-yocto 4.1/4.4. What kernel tree is that building ? upstream ? linux-yocto ? And if linux-yocto, what branch ? It is building linux-yocto 4.1. I have attached the compilation log, in case that helps. What I am doing is simply building a vexpress-qemu machine with poky's master, so it should be quite straightforward to reproduce. In particular, I am following our projects guide for creating a Mender build at https://github.com/mendersoftware/meta-mender/blob/master/README.md, but I don't think it reaches the Mender-specific layers. Thanks for the help and let me know if there's anything else you need. Bruce Thank you. -- Eystein DEBUG: Executing shell function do_compile NOTE: make -j 4 zImage CC=arm-poky-linux-gnueabi-gcc -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd LOADADDR=0x6080 CHK include/config/kernel.release GEN ./Makefile CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h Using /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source as source for kernel HOSTCC scripts/conmakehash HOSTCC scripts/sortextable MKELF scripts/mod/elfconfig.h CC scripts/mod/devicetable-offsets.s HOSTCC scripts/mod/sumversion.o In file included from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/compiler.h:54:0, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/uapi/linux/stddef.h:1, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/stddef.h:4, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/uapi/linux/posix_types.h:4, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/uapi/linux/types.h:13, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/types.h:5, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/mod_devicetable.h:11, from /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/scripts/mod/devicetable-offsets.c:2: /home/yocto/poky/build/tmp/work-shared/vexpress-qemu/kernel-source/include/linux/compiler-gcc.h:121:30: fatal error: linux/compiler-gcc6.h: No such file or directory #include gcc_header(__GNUC__) ^ compilation terminated. make[4]: *** [scripts/mod/devicetable-offsets.s] Error 1 make[4]: *** Waiting for unfinished jobs make[3]: *** [scripts/mod] Error 2 make[2]: *** [scripts] Error 2 make[1]: *** [sub-make] Error 2 make: *** [__sub-make] Error 2 ERROR: oe_runmake failed ERROR: Function failed: do_compile (log file is located at /home/yocto/poky/build/tmp/work/vexpress_qemu-poky-linux-gnueabi/linux-yocto/4.1.24+gitAUTOINC+46bb64d605_86093f78f6-r0/temp/log.do_compile.14419) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [eclipse-poky][PATCH v2] Documentation: add check for adt-manual vs sdk-manual build
[YOCTO #9622]
For older YP releases (prior to krogoth/2.1) adt-manual was the norm.
Since krogoth/2.1, sdk-manual should replace it.
- adt-manual dropped in commit 84abe03de1cff7952b5d0428e7433f094dde2b02
- sdk-manual added in commit ab591831a97a97d405d13ed75e9fb01e0452c292
Signed-off-by: Tim Orling
---
Changes since v1:
- check for presence of adt-manual removal commit for switch to sdk-manual
- should be less brittle than the prior "whitelist" branch/tag name approach
plugins/org.yocto.doc.user/about.html.in | 8
plugins/org.yocto.doc.user/plugin.xml| 2 +-
plugins/org.yocto.doc.user/toc.xml | 4 ++--
scripts/generate-doc.sh | 29 ++---
4 files changed, 33 insertions(+), 10 deletions(-)
diff --git a/plugins/org.yocto.doc.user/about.html.in
b/plugins/org.yocto.doc.user/about.html.in
index 3040859..5188d3c 100644
--- a/plugins/org.yocto.doc.user/about.html.in
+++ b/plugins/org.yocto.doc.user/about.html.in
@@ -53,12 +53,12 @@
- Yocto Project Application Developer's Guide:
+ Yocto Project Software Development Kit (SDK)
Developer's Guide:
- This manual shows you how to setup and use the
Application Development
- Toolkit (ADT) and stand-alone cross-development
toolchains so you can
+ This manual shows you how to setup and use the Software
Development
+ Kit (SDK) and stand-alone cross-development toolchains
so you can
develop user-space applications.
@@ -72,7 +72,7 @@
git://git.yoctoproject.org/yocto-docs
- Commit: @COMMIT_ID-adt-manual@
+ Commit: @COMMIT_ID-sdk-manual@
diff --git a/plugins/org.yocto.doc.user/plugin.xml
b/plugins/org.yocto.doc.user/plugin.xml
index 8e87ce7..c7754de 100644
--- a/plugins/org.yocto.doc.user/plugin.xml
+++ b/plugins/org.yocto.doc.user/plugin.xml
@@ -8,7 +8,7 @@
primary="true">
-
-
+
+
diff --git a/scripts/generate-doc.sh b/scripts/generate-doc.sh
index e3ac3d8..b817d4c 100755
--- a/scripts/generate-doc.sh
+++ b/scripts/generate-doc.sh
@@ -22,6 +22,15 @@ fail ()
exit ${retval}
}
+safe_sed()
+{
+ if [ "$1" ] && [ "$2" ]; then
+ sed -e "$1" $2 > $2.tmp && mv $2.tmp $2 || fail $? "safe_sed $1 $2"
+ else
+ fail 1 "usage: safe_sed \"s/from/to/\" /path/to/file"
+ fi
+}
+
CHECKOUT_TAG=0
while getopts ":h" opt; do
case $opt in
@@ -53,10 +62,24 @@ cd ${DOC_DIR}
git checkout $1 || fail $? "git checkout $1"
COMMIT_ID=`git rev-parse HEAD`
-# build and copy
-DOCS="yocto-project-qs adt-manual kernel-dev \
- bsp-guide ref-manual dev-manual profile-manual"
+# check yocto-docs branch/tag and build sdk-manual or adt-manual accordingly
+# [YOCTO #9622]
+ADT_REMOVAL_COMMIT=84abe03de1cff7952b5d0428e7433f094dde2b02
+if [ "$(git merge-base ${ADT_REMOVAL_COMMIT} $1)" = "${ADT_REMOVAL_COMMIT}" ];
then
+ DOCS="yocto-project-qs sdk-manual kernel-dev \
+bsp-guide ref-manual dev-manual profile-manual"
+else
+ DOCS="yocto-project-qs adt-manual kernel-dev \
+bsp-guide ref-manual dev-manual profile-manual"
+ safe_sed "s/sdk-manual/adt-manual/" ${DOC_PLUGIN_DIR}/plugin.xml
+ safe_sed "s/sdk-manual/adt-manual/" ${DOC_PLUGIN_DIR}/about.html.in
+ safe_sed "s/Software Development Kit (SDK)/Application/"
${DOC_PLUGIN_DIR}/about.html.in
+ safe_sed "s/(SDK)/(ADT)/" ${DOC_PLUGIN_DIR}/about.html.in
+ safe_sed "s/sdk-manual/adt-manual/" ${DOC_PLUGIN_DIR}/toc.xml
+ safe_sed "s/Software Development Kit (SDK)/Application/"
${DOC_PLUGIN_DIR}/toc.xml
+fi
+# build and copy
cd documentation
for DOC in ${DOCS}; do
make DOC=${DOC} eclipse
--
2.5.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to set a cmake cache variable to a spezific value?
Hi, Just add to recipe: inherit cmake EXTRA_OECMAKE += " -DVARIABLE_NAME=value" On Thu, Jun 2, 2016 at 4:24 PM, Burton, Ross wrote: > > 2016-05-30 12:59 GMT+01:00 : > >> I want to build a recipe for a cmake based application. To make it run I >> need to set a cached cmake variable. >> > > EXTRA_OECMAKE += "-DVARIABLE_NAME=value" > > Ross > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to set a cmake cache variable to a spezific value?
2016-05-30 12:59 GMT+01:00 : > I want to build a recipe for a cmake based application. To make it run I > need to set a cached cmake variable. > EXTRA_OECMAKE += "-DVARIABLE_NAME=value" Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] dev package being pulled into RDEPENDS automatically
On 31 May 2016 at 12:09, Alfonso Lima Astor wrote: > Do you know where this rdependency could get pulled into? how could I > remove it? > This can happen if the package generates unversioned libraries that look like development symlinks (such as /usr/lib/libfoo.so), which by default get packaged into foo-dev but as they're real libraries will result in dependencies being added. If this is the case then you just need to fix the packaging so the real libraries are not in the -dev package. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [matchbox-desktop-sato][PATCH] Remove Utilities-folder
On 2 June 2016 at 10:03, Jussi Kukkonen wrote: > Typical result of separate Applications and Utilities is that > Applications only contains a single icon. Applications is also > the default folder: it's a waste of space to have that empty. > > Merge all Utilities into Applications. > Reviewed-by: Ross Burton -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Recipe Debug - QA Issue
Also, try this to get KERNEL_VERSION:
KERNEL_VERSION="${@base_read_file('${STAGING_KERNEL_BUILDDIR}/kernel-abiversion')
kmoddir =
"/lib/modules/${KERNEL_VERSION}/kernel/drivers/net/wireless/redpine"
On Wed, Jun 1, 2016 at 8:44 PM, Paul DeMetrotion <
pdemetrot...@winsystems.com> wrote:
> That removed the QA error. Thanks you.
>
>
>
> Problems remain because none of the 12 driver files are being copied to
> the image while the two shell script files are copied.
>
>
>
> Paul DeMetrotion
>
> Software Guru
>
> WinSystems, Inc.
>
> (972) 571-8657
>
> www.winsystems.com
>
>
>
> *From:* Oleksandr Poznyak [mailto:oleksandr.pozn...@gmail.com]
> *Sent:* Wednesday, June 01, 2016 11:20 AM
>
> *To:* Paul DeMetrotion
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Recipe Debug - QA Issue
>
>
>
> oops!
>
> FILES_${PN} += "${base_libdir}"
>
> That's it
>
>
>
> On Wed, Jun 1, 2016 at 6:42 PM, Paul DeMetrotion <
> pdemetrot...@winsystems.com> wrote:
>
> Thanks for your suggestions. I changed it to the simple one-line
> modification but still have the same issue. I even commented the
> FILES_${PN} line and have the same issue. It appears that the problem is
> with the do_install_append() section.
>
>
>
> Paul DeMetrotion
>
> Software Guru
>
> WinSystems, Inc.
>
> (972) 571-8657
>
> www.winsystems.com
>
>
>
> *From:* Oleksandr Poznyak [mailto:oleksandr.pozn...@gmail.com]
> *Sent:* Wednesday, June 01, 2016 8:40 AM
> *To:* Paul DeMetrotion
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Recipe Debug - QA Issue
>
>
>
> Hi,
> 1) It's more common to use FILES_${PN} += ...
> 2) Please, remove ${D} from FILES_${PN}
>
> Try this:
>
> FILES_${PN} += " \
> ${kmoddir}/onebox_common_gpl.ko \
> ${kmoddir}/onebox_gpl.ko \
> ${kmoddir}/onebox_nongpl.ko \
> ${kmoddir}/onebox_wlan_gpl.ko \
> ${kmoddir}/onebox_wlan_nongpl.ko \
> ${kmoddir}/wlan.ko \
> ${kmoddir}/wlan_wep.ko \
> ${kmoddir}/wlan_ccmp.ko \
> ${kmoddir}/wlan_tkip.ko \
> ${kmoddir}/wlan_acl.ko \
> ${kmoddir}/wlan_scan_sta.ko \
> ${kmoddir}/wlan_xauth.ko \
> /etc/redpine/wlan_enable.sh \
> /etc/redpine/wlan_disable.sh \
> "
>
> Moreover, You may simplify it:
>
> FILES_${PN} += "${kmoddir} /etc/redpine"
>
>
>
> On Wed, Jun 1, 2016 at 3:55 PM, Paul DeMetrotion <
> pdemetrot...@winsystems.com> wrote:
>
> I have created a simple (?) recipe to copy some existing drivers and
> scripts into my kernel image. I am getting the following error when I
> attempt to bitbake the recipe. Is this a license issue?
>
>
>
> ERROR: QA Issue: rs9113: Files/directories were installed but not shipped
>
> /lib
>
> /lib/modules
>
> /lib/modules/kernel
>
> /lib/modules/kernel/drivers
>
> /lib/modules/kernel/drivers/net
>
> /lib/modules/kernel/drivers/net/wireless
>
> /lib/modules/kernel/drivers/net/wireless/redpine
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan_ccmp.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/onebox_common_gpl.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan_tkip.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan_wep.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan_scan_sta.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan_acl.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/onebox_wlan_nongpl.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/onebox_wlan_gpl.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/wlan_xauth.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/onebox_gpl.ko
>
> /lib/modules/kernel/drivers/net/wireless/redpine/onebox_nongpl.ko
> [installed-vs-shipped]
>
>
>
> Here is the recipe. I have all of the files to be copied in the same
> directory as the recipe.
>
>
>
> DESCRIPTION = "Install of redpine drivers and scripts"
>
>
>
> LICENSE = "MIT"
>
> LIC_FILES_CHKSUM =
> "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
>
>
> file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
>
>
>
> kmoddir =
> "/lib/modules/${KERNEL_VERSION}/kernel/drivers/net/wireless/redpine"
>
>
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
>
>
> SRC_URI_append = " \
>
> file://onebox_common_gpl.ko \
>
> file://onebox_gpl.ko \
>
> file://onebox_nongpl.ko \
>
> file://onebox_wlan_gpl.ko \
>
> file://onebox_wlan_nongpl.ko \
>
> file://wlan.ko \
>
> file://wlan_wep.ko \
>
> file://wlan_ccmp.ko \
>
> file://wlan_tkip.ko \
>
> file://wlan_acl.ko \
>
> file://wlan_scan_sta.ko \
>
> file://wlan_xauth.ko \
>
> file://wlan_enable.sh \
>
> file://wlan_disable.sh \
>
> "
>
>
>
> do_install_append() {
>
> mkdir -p ${D}${kmoddir}
>
> install -m 0755 ${WORKDIR}/onebox_common_gpl.ko ${D}${kmoddir}
>
> install -m 0755 ${WORKDIR}/onebox_gpl.ko ${D}${kmoddir}
>
> install -m 0755 ${WORKDIR}/onebox_nongpl.ko ${D}${kmoddir}
>
> install -m 0755 ${WORK
Re: [yocto] [meta-cgl][PATCH 1/2] Added device manager multipath support for root file system
On ons, 2016-05-11 at 15:15 +, Alexandru Vaduva wrote:
> Hello Adi,
>
> Cannot this two patches be redone by:
>removing from "[PATCH 1/2] Added device manager
> multipath support for root file system" the line "+IMAGE_CLASSES +=
> "image_types_uboot""
>only keeping in "[PATCH 2/2] distro: Move IMAGE_CLASSES
> inheritance" the line from " poky-cgl.conf".
>
>
> Also this patch has both require and inherit and in my opinion the
> inherit line can be removed since the core-image-cgl also adds it
> indirectly.
>
>
> Another objection for this patch is that it should be broken in more
> pieces: multipath, images, initrdscripts and conf_setup or in another
> format. Having it like this is too big and in case of a revert too
> much functionality could be lost or replicated.
You're probably right it would be good to rework this patch, but since
I'm not the original author and I don't have allocated time for it these
days it may be a while until I can get around to do it.
I'll merge the other two regarding Selinux though.
--Adrian
>
>
> Thanks,
> Alex V.
>
>
>
>
> On Tuesday, May 10, 2016 1:08 PM, Adrian Dudau
> wrote:
>
>
>
> From: Mats Liljegren
>
> This is implemented using an initramfs, built by
> core-image-cgl-initramfs image
> recipe. Multipath device configurations are done using kernel boot
> parameters.
> The multipath-root-howto.md explains how to use this.
>
> Also note that the meta-cgl/scripts/conf_setup.sh will now also add a
> BBMASK
> entry to mask out the meta-virtualization's version of
> multipath-tools, since
> we need the newer recipe in the meta-openembedded/meta-oe instead.
>
> Signed-off-by: Mats Liljegren
> Signed-off-by: Adrian Dudau
> ---
> meta-cgl-common/images/core-image-cgl-initramfs.bb | 22 +++
> meta-cgl-common/images/core-image-cgl.bb | 2 +
> .../packagegroups/packagegroup-cgl-middleware.bb | 8 +-
> .../recipes-core/initrdscripts/files/init-boot.sh | 179
> +
> .../initrdscripts/initramfs-cgl-boot_1.0.bb| 14 ++
> scripts/conf_setup.sh | 2 +
> 6 files changed, 220 insertions(+), 7 deletions(-)
> create mode 100644 meta-cgl-common/images/core-image-cgl-initramfs.bb
> create mode 100644
> meta-cgl-common/recipes-core/initrdscripts/files/init-boot.sh
> create mode 100644
> meta-cgl-common/recipes-core/initrdscripts/initramfs-cgl-boot_1.0.bb
> create mode 100755 scripts/conf_setup.sh
>
> diff --git a/meta-cgl-common/images/core-image-cgl-initramfs.bb
> b/meta-cgl-common/images/core-image-cgl-initramfs.bb
> new file mode 100644
> index 000..845fa07
> --- /dev/null
> +++ b/meta-cgl-common/images/core-image-cgl-initramfs.bb
> @@ -0,0 +1,22 @@
> +require core-image-cgl.bb
> +
> +# Recipe is based on core-image-minimal.bb
> +DESCRIPTION = "Initramfs used to mount multipath device as root file
> system"
> +
> +PACKAGE_INSTALL = "initramfs-cgl-boot busybox base-passwd udev
> ${ROOTFS_BOOTSTRAP_INSTALL}"
> +
> +# Do not pollute the initrd image with rootfs features
> +IMAGE_FEATURES = ""
> +
> +export IMAGE_BASENAME = "core-image-cgl-initramfs"
> +IMAGE_LINGUAS = ""
> +
> +LICENSE = "MIT"
> +
> +IMAGE_FSTYPES = "cpio.gz.u-boot"
> +IMAGE_CLASSES += "image_types_uboot"
> +inherit core-image
> +
> +IMAGE_ROOTFS_SIZE = "8192"
> +
> +BAD_RECOMMENDATIONS += "busybox-syslog"
> diff --git a/meta-cgl-common/images/core-image-cgl.bb
> b/meta-cgl-common/images/core-image-cgl.bb
> index d12391b..5975601 100644
> --- a/meta-cgl-common/images/core-image-cgl.bb
> +++ b/meta-cgl-common/images/core-image-cgl.bb
> @@ -21,6 +21,8 @@ IMAGE_INSTALL += "\
> kernel-modules \
> "
>
> +IMAGE_FSTYPES += " ext3.gz"
> +
> # kexec-tools doesn't work on Mips
> KEXECTOOLS_mips ?= ""
> KEXECTOOLS_mipsel ?= ""
> diff --git
> a/meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb
> b/meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb
> index 448e038..b0c2cac 100644
> --- a/meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb
> +++ b/meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb
> @@ -18,14 +18,8 @@ DHCP = " \
> "
>
> MULTIPATH_TOOLS = " \
> -libmpathpersist \
> -mpathpersist \
> +multipath-tools \
> kpartx \
> -libmultipath \
> -multipath \
> -multipathd \
> -libmultipath-dev \
> -libmpathpersist-dev \
> "
>
> RDEPENDS_packagegroup-cgl-middleware = "\
> diff --git
> a/meta-cgl-common/recipes-core/initrdscripts/files/init-boot.sh
> b/meta-cgl-common/recipes-core/initrdscripts/files/init-boot.sh
> new file mode 100644
> index 000..fcadfc6
> --- /dev/null
> +++ b/meta-cgl-common/recipes-core/initrdscripts/files/init-boot.sh
> @@ -0,0 +1,179 @@
> +#!/bin/sh -eu
> +
> +# Fail function, either called explicitly or when shell will quit
> +fail () {
> +# Avoid recursive traps
> +trap '' ERR EXIT
> +
> +# If message provided, print it
> +[ -n '${1:-}' ] && echo $@
> +
> +# Gene
[yocto] [matchbox-desktop-sato][PATCH] Remove Utilities-folder
Typical result of separate Applications and Utilities is that Applications only contains a single icon. Applications is also the default folder: it's a waste of space to have that empty. Merge all Utilities into Applications. Signed-off-by: Jussi Kukkonen --- This is a partial fix for [YOCTO #9667] in that a typical core-image-sato will have Terminal and File Manager icons visible on the initial screen now, making it easier for newcomers to find them and allowing faster access to common tools for everyone. Applications.directory | 2 +- Makefile.am| 3 +-- Root.order | 1 - Utilities.directory| 8 4 files changed, 2 insertions(+), 12 deletions(-) delete mode 100644 Utilities.directory diff --git a/Applications.directory b/Applications.directory index 69f6ed1..a7e3501 100644 --- a/Applications.directory +++ b/Applications.directory @@ -3,4 +3,4 @@ Name=Applications Comment=Applications Icon=gnome-applications.png Type=Directory -Match=AudioVideo;Audio;Video;Graphics;Network;Office;meta-fallback; +Match=AudioVideo;Audio;Video;Graphics;Network;Office;Utility;System;Development;meta-fallback; diff --git a/Makefile.am b/Makefile.am index c4f4667..4e6cae2 100644 --- a/Makefile.am +++ b/Makefile.am @@ -4,5 +4,4 @@ dist_folder_DATA = \ All.directory \ Applications.directory \ Games.directory \ - Settings.directory \ - Utilities.directory + Settings.directory diff --git a/Root.order b/Root.order index 0c2f3cb..01a86d2 100644 --- a/Root.order +++ b/Root.order @@ -1,5 +1,4 @@ Applications -Utilities Games Settings All diff --git a/Utilities.directory b/Utilities.directory deleted file mode 100644 index 1a73e63..000 --- a/Utilities.directory +++ /dev/null @@ -1,8 +0,0 @@ -[Desktop Entry] -Name=Utilities -Name[de]=Einstellungen -Comment=Various utilities -Comment[de]=Verschiedene Hilfsprogramme -Icon=mbfolder.png -Type=Directory -Match=Utility;System;Development; -- 2.8.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
