Re: [yocto] [PATCH] Perl: fix PERL5LIB settings
Hi Wolfgang, On 5 November 2014 19:29, Wolfgang Denk w...@denx.de wrote: meta/recipes-devtools/perl/perl-native_5.14.3.bb | 4 ++-- meta/recipes-devtools/perl/perl_5.14.3.bb| 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) Perl was upgraded to 5.20.0 in July, can you rebase and verify that this is still required? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build issue with daisy branch
On Thursday 06 November 2014 16:01:44 Pierre Yves MORDRET wrote: Recently I came across a build issue when using daisy branch. ports/linux/xattr/portdefs.h:1:24: fatal error: attr/xattr.h: No such file or directory #include attr/xattr.h ERROR: Function failed: do_compile (log file is located at .../tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-pseudo/1.6.2-r0/ temp/log.do_compile.26354) I saw an upgrade in daisy branch related to pseudo. Do you know which package is supposed to provide attr/xattr.h This has been subsequently fixed in the daisy branch - if you pull again you should get the fix. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build issue with daisy branch
On Fri, Nov 7, 2014 at 9:15 AM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, Nov 7, 2014 at 9:05 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Thursday 06 November 2014 16:01:44 Pierre Yves MORDRET wrote: Recently I came across a build issue when using daisy branch. ports/linux/xattr/portdefs.h:1:24: fatal error: attr/xattr.h: No such file or directory #include attr/xattr.h ERROR: Function failed: do_compile (log file is located at .../tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-pseudo/1.6.2-r0/ temp/log.do_compile.26354) I saw an upgrade in daisy branch related to pseudo. Do you know which package is supposed to provide attr/xattr.h This has been subsequently fixed in the daisy branch - if you pull again you should get the fix. Cheers, Paul I too noticed something strange in my first dizzy build. I stole a line from my previous local.conf: IMAGE_FSTYPES ?= jffs2 ubi tar.bz2 ... and the build failed with all kinds of ubi related errors. Regards, Brian OK, forgive me. I'm still asleep. Didn't notice the OP was talking about daisy. I had dizzy on the brain. B -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build issue with daisy branch
On Fri, Nov 7, 2014 at 9:05 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Thursday 06 November 2014 16:01:44 Pierre Yves MORDRET wrote: Recently I came across a build issue when using daisy branch. ports/linux/xattr/portdefs.h:1:24: fatal error: attr/xattr.h: No such file or directory #include attr/xattr.h ERROR: Function failed: do_compile (log file is located at .../tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-pseudo/1.6.2-r0/ temp/log.do_compile.26354) I saw an upgrade in daisy branch related to pseudo. Do you know which package is supposed to provide attr/xattr.h This has been subsequently fixed in the daisy branch - if you pull again you should get the fix. Cheers, Paul I too noticed something strange in my first dizzy build. I stole a line from my previous local.conf: IMAGE_FSTYPES ?= jffs2 ubi tar.bz2 ... and the build failed with all kinds of ubi related errors. Regards, Brian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: gtest not found in the base feed
On Thu, Nov 06, 2014 at 04:26:15PM -0700, Gary Thomas wrote:
On 2014-11-06 16:01, Kevyn-Alexandre Paré wrote:
Hi,
I'm just trying to add a recipe that I found here
https://github.com/webOS-ports/meta-webos-ports/blob/master/recipes-upstreamable/gtest/gtest_1.7.0.bb
for gtest as part of my image:
bitbake -e gtest | grep ^PACKAGES=
PACKAGES=gtest-dbg gtest-staticdev gtest-dev gtest-doc gtest-locale gtest
Adding it:
IMAGE_INSTALL += gtest
ERROR: gtest not found in the base feeds (overo armv7a-vfp-neon
armv7a-vfp armv7a armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5
armv4 arm noarch any all).
Since in
ls
tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/deploy-rpms/armv7a_vfp_neon/
gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm
gtest-dev-1.7.0-r0.armv7a_vfp_neon.rpm
Where is the gtest-1.7.0-r0.armv7a_vfp_neon.rpm??
I suspect that the build didn't work correctly, or at least it generated
no installable objects which by default will not generate an empty package.
That's correct, all files are installed in gtest-dev package.
The problem is the default RDEPENDS from ${PN}-dev to ${PN}
meta/conf/bitbake.conf:RDEPENDS_${PN}-dev = ${PN} (= ${EXTENDPKGV})
You can either set
ALLOW_EMPTY_${PN} = 1
or
RDEPENDS_${PN}-dev =
tree
tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/packages-split/
tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/packages-split/
├── gtest
├── gtest-dbg
├── gtest-dev
│ └── usr
│ ├── include
│ │ └── gtest
│ │ ├── gtest-death-test.h
│ │ ├── gtest.h
│ │ ├── gtest-message.h
│ │ ├── gtest-param-test.h
│ │ ├── gtest_pred_impl.h
│ │ ├── gtest-printers.h
│ │ ├── gtest_prod.h
│ │ ├── gtest-spi.h
│ │ ├── gtest-test-part.h
│ │ ├── gtest-typed-test.h
│ │ └── internal
│ │ ├── gtest-death-test-internal.h
│ │ ├── gtest-filepath.h
│ │ ├── gtest-internal.h
│ │ ├── gtest-linked_ptr.h
│ │ ├── gtest-param-util-generated.h
│ │ ├── gtest-param-util.h
│ │ ├── gtest-port.h
│ │ ├── gtest-string.h
│ │ ├── gtest-tuple.h
│ │ └── gtest-type-util.h
│ └── src
│ └── gtest
│ ├── cmake
│ │ └── internal_utils.cmake
│ ├── CMakeLists.txt
│ └── src
│ ├── gtest-all.cc
│ ├── gtest.h
│ └── gtest_main.cc
├── gtest-doc
├── gtest-locale
└── gtest-staticdev
I replace gtest with gtest-dev.
ERROR: Unable to install packages. Command
'/home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/sysroots/x86_64-linux/usr/bin/smart
--data-dir=/home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/work/overo-poky-linux-gnueabi/builder-console-image/1.0-r0/rootfs/var/lib/smart
install -y alsa-utils@armv7a_vfp_neon psplash@armv7a_vfp_neon
mtdev@armv7a_vfp_neon tar@armv7a_vfp_neon less@armv7a_vfp_neon
iputils@armv7a_vfp_neon mtd-utils-ubifs@armv7a_vfp_neon
sudo@armv7a_vfp_neon nirsd@armv7a_vfp_neon u-boot-fw-utils@overo
raw2rgbpnm@armv7a_vfp_neon vim@armv7a_vfp_neon
media-ctl@armv7a_vfp_neon findutils@armv7a_vfp_neon
rpm@armv7a_vfp_neon cpufrequtils@armv7a_vfp_neon
packagegroup-cli-tools@all bzip2@armv7a_vfp_neon
v4l-utils@armv7a_vfp_neon cmake@armv7a_vfp_neon nano@armv7a_vfp_neon
g++-symlinks@armv7a_vfp_neon gcc-dev@armv7a_vfp_neon
gcc-doc@armv7a_vfp_neon psplash-brainsight@armv7a_vfp_neon tzdata@all
coreutils@armv7a_vfp_neon g++@armv7a_vfp_neon gcov@armv7a_vfp_neon
init-ifupdown@overo tcpdump@armv7a_vfp_neon
systemd-analyze@armv7a_vfp_neon packagegroup-core-boot@overo
memtester@armv7a_vfp_neon yavta@armv7a_vfp_neon
cpp-symlinks@armv7a_vfp_neon libts-1.0-0@armv7a_vfp_neon
gcc-plugin-dev@armv7a_vfp_neon gzip@armv7a_vfp_neon
packagegroup-core-ssh-openssh@all ntp@armv7a_vfp_neon
libev4@armv7a_vfp_neon packagegroup-cli-tools-debug@all
gcc@armv7a_vfp_neon u-boot@overo cpp@armv7a_vfp_neon
gtest-dev@armv7a_vfp_neon iw@armv7a_vfp_neon wget@armv7a_vfp_neon
shadow@armv7a_vfp_neon zygoted@armv7a_vfp_neon
gcc-plugins@armv7a_vfp_neon grep@armv7a_vfp_neon zip@armv7a_vfp_neon
diffutils@armv7a_vfp_neon valgrind@armv7a_vfp_neon
linux-firmware-sd8787@all linux-firmware-sd8686@all
smartpm@armv7a_vfp_neon gcc-dbg@armv7a_vfp_neon
gcc-symlinks@armv7a_vfp_neon packagegroup-base-extended@overo
u-boot-mkimage@armv7a_vfp_neon base-passwd@armv7a_vfp_neon
locale-base-en-us@armv7a_vfp_neon' returned 1:
Loading cache...
Updating cache...
[100%]
Computing transaction...error: Can't install
Re: [yocto] ERROR: gtest not found in the base feed
On 7 November 2014 14:23, Martin Jansa martin.ja...@gmail.com wrote:
You can either set
ALLOW_EMPTY_${PN} = 1
or
RDEPENDS_${PN}-dev =
FWIW, I'm a *massive* fan of using RDEPENDS here - instead of creating
empty packages which will only confuse in the future, remove the dependency
that is problematic.
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Error while trying to setup using ADT installer
Hi, I was trying to setup Yocto 1.7 released development environment but while the ADT installer tries to download files it get error as 403 forbidden. Below is the snapshot of the same. Snip [ADT_INST] Please enter your selections here: I Spider mode enabled. Check if remote file exists. --2014-11-06 16:02:03-- http://adtrepo.yoctoproject.org//1.7 Resolving adtrepo.yoctoproject.org... 140.211.169.59 Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://adtrepo.yoctoproject.org/1.7/ [following] Spider mode enabled. Check if remote file exists. --2014-11-06 16:02:04-- http://adtrepo.yoctoproject.org/1.7/ Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Remote file exists and could contain further links, but recursion is disabled -- not retrieving. OPKG is not setup, setting up opkg in local, which is required for installing yocto ADT... Configure opkg ... Make opkg ... Make Install opkg ... Successfully installed OPKG. Creating new images downloading folder: ./download_image ... Downloading file: zImage-qemuarm.bin... --2014-11-06 16:02:25-- http://adtrepo.yoctoproject.org//1.7/rootfs/qemuarm/zImage-qemuarm.bin Resolving adtrepo.yoctoproject.org... 140.211.169.59 Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-11-06 16:02:27 ERROR 403: Forbidden. Downloading file: core-image-minimal-qemuarm.tar.bz2... --2014-11-06 16:02:27-- http://adtrepo.yoctoproject.org//1.7/rootfs/qemuarm/core-image-minimal-qemuarm.tar.bz2 Resolving adtrepo.yoctoproject.org... 140.211.169.59 Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-11-06 16:02:28 ERROR 403: Forbidden. . . . Downloading file: core-image-sato-sdk-qemux86.tar.bz2... --2014-11-06 16:02:29-- http://adtrepo.yoctoproject.org//1.7/rootfs/qemux86/core-image-sato-sdk-qemux86.tar.bz2 Resolving adtrepo.yoctoproject.org... 140.211.169.59 Connecting to adtrepo.yoctoproject.org|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-11-06 16:02:29 ERROR 403: Forbidden. Start installing selected native ADT for archs: arm x86... ### Please note from this point on installation requires sudo password ... ### [sudo] password for test: Successfully create directory /opt/poky/1.7//var/lib/opkg. Updating opkg... /snip I have even tried to open aboye URLs through browser still I get the same error. So any thoughts to fix this issue as I am using adt_installer.tar.bz2 for the same. Thanks, Abhinav -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Test in do_patch() fails for annotated tags
Commit 92c1ece6c347030d48995a36f4c67861356e59d3 causes the test in
do_patch() in kernel-yocto.bbclass to fail if ${machine_srcrev} is an
annotated tag. The check is meant to ensure that ${machine_srcrev} is an
ancestor of HEAD, but if ${machine_srcrev} is a tag, then $(git
rev-parse --verify ${machine_srcrev}) evaluates to the SHA of the tag
instead of what it's pointing to.
Replacing $(git rev-parse --verify ${machine_srcrev}) with $(git
rev-parse --verify ${machine_srcrev}~0) seems to fix the problem. See
http://stackoverflow.com/a/1863712/1454667
--
Jeff Wang
smime.p7s
Description: S/MIME Cryptographic Signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can not generate the ccgi-${PV} package
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of neil...@emerson.com
Sent: Friday, November 07, 2014 10:44 AM
To: yocto@yoctoproject.org
Subject: [yocto] Can not generate the ccgi-${PV} package
Hi, all
I try to compile libccgi .
At end , I don't why can't create the standard ccgi-${PV} package.
The just create ccgi-dbg-${PV} ccgi-dev-${PV}, do you know why??
The following is my recipes .bb file:
SUMMARY = Add ccgi lib to rootfs
HOMEPAGE = http://sourceforge.net/projects/libccgi/?source=typ_redirect;
LICENSE = GPLv2
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
LIC_FILES_CHKSUM =
file://COPYING;md5=d32239bcb673463ab874e80d47fae504file:///\\COPYING;md5=d32239bcb673463ab874e80d47fae504
FILES_${PN} = /usr \
/usr/include \
/usr/lib \
/usr/include/ccgi.h \
/usr/lib/libccgi.so \
SRC_URI = file://${PN}-${PV}.tar.gzfile:///\\$%7bPN%7d-$%7bPV%7d.tar.gz
S = ${WORKDIR}/${PN}-${PV}
PARALLEL_MAKEINST=prefix=${D}/usr
EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX}'
do_install () {
install -d ${D}${includedir}
install -d ${D}${libdir}
install -m 0755 ${S}/*.h ${D}${includedir}
install -m 0755 ${S}/*.so ${D}${libdir}
}
There is no file to be packaged as ${PN}. You can added below line to generate
it.
ALLOW_EMPTY_${PN} = 1
-Ting
Thank youBest regards
Neil Wu
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Test in do_patch() fails for annotated tags
Jeff and I have already exchanged email on this yesterday. While using a tag
for the SRCREV is not typically something we suggest .. tweaking the
ancestor check is fine in this case, since it works in both scenarios.
I have a patch queued to address this, and am soaking it now.
Bruce
On Thu, Nov 6, 2014 at 6:12 PM, Jeff Wang jeffrey.w...@ll.mit.edu wrote:
Commit 92c1ece6c347030d48995a36f4c67861356e59d3 causes the test in
do_patch() in kernel-yocto.bbclass to fail if ${machine_srcrev} is an
annotated tag. The check is meant to ensure that ${machine_srcrev} is an
ancestor of HEAD, but if ${machine_srcrev} is a tag, then $(git rev-parse
--verify ${machine_srcrev}) evaluates to the SHA of the tag instead of what
it's pointing to.
Replacing $(git rev-parse --verify ${machine_srcrev}) with $(git
rev-parse --verify ${machine_srcrev}~0) seems to fix the problem. See
http://stackoverflow.com/a/1863712/1454667
--
Jeff Wang
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build issue with daisy branch
Thanks ! I'm going to check that. In the meantime, I had a quick look on the openembedded-core folder but I didn't see any meaningful commits from the branch that could solve this issue. Can you just give more insight on how it has been fixed ? Thanks in advance -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: vendredi 7 novembre 2014 09:05 To: Pierre Yves MORDRET Cc: yocto@yoctoproject.org Subject: Re: [yocto] Build issue with daisy branch On Thursday 06 November 2014 16:01:44 Pierre Yves MORDRET wrote: Recently I came across a build issue when using daisy branch. ports/linux/xattr/portdefs.h:1:24: fatal error: attr/xattr.h: No such file or directory #include attr/xattr.h ERROR: Function failed: do_compile (log file is located at .../tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-pseudo/1.6. 2-r0/ temp/log.do_compile.26354) I saw an upgrade in daisy branch related to pseudo. Do you know which package is supposed to provide attr/xattr.h This has been subsequently fixed in the daisy branch - if you pull again you should get the fix. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: gtest not found in the base feed
Hi Gary, On Thu, Nov 6, 2014 at 6:26 PM, Gary Thomas g...@mlbassoc.com wrote: On 2014-11-06 16:01, Kevyn-Alexandre Paré wrote: ls tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/deploy-rpms/armv7a_vfp_neon/ gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm gtest-dev-1.7.0-r0.armv7a_vfp_neon.rpm Where is the gtest-1.7.0-r0.armv7a_vfp_neon.rpm?? This is a part that I don't yet understand about packaging... Why the gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm is there and empty and and other empty package are not? I think I have read that -dbg is always there ? Anyone can point my to documentation about that didn't found it. I suspect that the build didn't work correctly, or at least it generated no installable objects which by default will not generate an empty package. hmm thx -KA -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: gtest not found in the base feed
On Fri, Nov 07, 2014 at 06:11:47PM -0500, Kevyn-Alexandre Paré wrote:
Hi Gary,
On Thu, Nov 6, 2014 at 6:26 PM, Gary Thomas g...@mlbassoc.com wrote:
On 2014-11-06 16:01, Kevyn-Alexandre Paré wrote:
ls
tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/deploy-rpms/armv7a_vfp_neon/
gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm
gtest-dev-1.7.0-r0.armv7a_vfp_neon.rpm
Where is the gtest-1.7.0-r0.armv7a_vfp_neon.rpm??
This is a part that I don't yet understand about packaging... Why the
gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm is there and empty and and
other empty package are not? I think I have read that -dbg is always
there ? Anyone can point my to documentation about that didn't found
it.
I don't know about any documentation of this, but there is:
meta/conf/bitbake.conf:ALLOW_EMPTY_${PN}-dev = 1
meta/conf/bitbake.conf:ALLOW_EMPTY_${PN}-dbg = 1
and ${PN}-dev and ${PN}-dbg are in default PACKAGES value, that's what
makes them always created (even when empty), unless the recipe defines
PACKAGES variable (not recommended).
The default runtime dependency from PN-dev is IMHO more annoying than
PN-dev existence.
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: gtest not found in the base feed
Martin,
On Fri, Nov 7, 2014 at 9:23 AM, Martin Jansa martin.ja...@gmail.com wrote:
On Thu, Nov 06, 2014 at 04:26:15PM -0700, Gary Thomas wrote:
On 2014-11-06 16:01, Kevyn-Alexandre Paré wrote:
Hi,
I'm just trying to add a recipe that I found here
https://github.com/webOS-ports/meta-webos-ports/blob/master/recipes-upstreamable/gtest/gtest_1.7.0.bb
for gtest as part of my image:
bitbake -e gtest | grep ^PACKAGES=
PACKAGES=gtest-dbg gtest-staticdev gtest-dev gtest-doc gtest-locale
gtest
Adding it:
IMAGE_INSTALL += gtest
ERROR: gtest not found in the base feeds (overo armv7a-vfp-neon
armv7a-vfp armv7a armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5
armv4 arm noarch any all).
Since in
ls
tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/deploy-rpms/armv7a_vfp_neon/
gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm
gtest-dev-1.7.0-r0.armv7a_vfp_neon.rpm
Where is the gtest-1.7.0-r0.armv7a_vfp_neon.rpm??
I suspect that the build didn't work correctly, or at least it generated
no installable objects which by default will not generate an empty package.
That's correct, all files are installed in gtest-dev package.
The problem is the default RDEPENDS from ${PN}-dev to ${PN}
meta/conf/bitbake.conf:RDEPENDS_${PN}-dev = ${PN} (= ${EXTENDPKGV})
k now I understand more this one:
Computing transaction...error: Can't install
gtest-dev-1.7.0-r0@armv7a_vfp_neon: no package provides gtest =
1.7.0-r0
198 EXTENDPRAUTO = ${@['.${PRAUTO\x7d',''][d.getVar('PRAUTO',1) is None]}
199 PRAUTOINX = ${PF}
200
201 PKGV ?= ${PV}
202 PKGR ?= ${PR}${EXTENDPRAUTO}
203 PKGE ?= ${@['','${PE\x7d'][int(d.getVar('PE',1) or 0) 0]}
204 EXTENDPKGEVER = ${@['','${PKGE\x7d:'][d.getVar('PKGE',1).strip() != '']}
205 EXTENDPKGV ?= ${EXTENDPKGEVER}${PKGV}-${PKGR}
So this EXTENDPKGEVER is :
-1.7.0-r0.armv7a_vfp_neon
?
You can either set
ALLOW_EMPTY_${PN} = 1
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-ALLOW_EMPTY
Adding this in my recipe and gtest-dev in my image create gtest
package and it succeed in creating the rootfs.
build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gtest/1.7.0-r0/deploy-rpms/armv7a_vfp_neon$
ls
gtest-1.7.0-r0.armv7a_vfp_neon.rpm
gtest-dbg-1.7.0-r0.armv7a_vfp_neon.rpm
gtest-dev-1.7.0-r0.armv7a_vfp_neon.rpm
or
RDEPENDS_${PN}-dev =
That works nicely but why this is not part of the recipe by default?
Could it be interesting to add it?
thx,
-KA
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
