[yocto] Cannot add libsrtp to yocto image
Hi,I need to add libsrtp to my yocto image. So I added libsrtp to "IMAGE_INSTALL". But I faced the following errors: Unknown package 'libsrtp'. Collected errors: * opkg_solver_install: Cannot install package libsrtp. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding debug output in recipe
Hi Anuj, "bitbake -e" is very useful for debugging out-of-tree build issue. However, looks like I have another issue. From "devtool build" output, I could see variables passed into makefile. Let's focus on "CC" for now: CC=x86_64-poky-linux-gcc -fuse-ld=bfd If we compare this to "bitbake -e" dump: export CC="x86_64-poky-linux-gcc -m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2 --sysroot=/a/ryeung/dev/yocto-git/yocto_build/build/tmp/sysroots/intel-corei7-64" You can see somehow the variable is modified. Let's focus on --sysroot portion. Without it, there seems to be no way for me to control LIBRARY_PATH's value. The result is that the linker couldn't find crti.o and a few other files. By manually adding back --sysroot portion, I could now get past this failure, onto the next. I suppose, as a possible final solution, I could do: $(CC) --sysroot=$(KERNEL_SRC) ... I'm really looking for simpler, more intuitive solution. What about the missing "-m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2" in the export? Raymond From: Anuj Mittal Sent: Thursday, April 5, 2018 9:52 PM To: Raymond Yeung; yocto@yoctoproject.org Subject: Re: [yocto] Adding debug output in recipe On 04/05/2018 03:33 PM, Raymond Yeung wrote: > Is there a way to add simple debug output (ideally don't need to control > debug level) to echo out values of variables? I tried the bb.xxx > variants, but couldn't get them to work. > To find out what a variable is being set to, you can try: bitbake -e Please see: https://wiki.yoctoproject.org/wiki/Technical_FAQ#I_set_a_variable_but_it_doesn.27t_seem_to_be_having_an_effect.2C_how_do_I_fix_this.3F Is that what you were looking for? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding debug output in recipe
You're right on. KERNEL_CC was used. The 3rd party code actually has 3
components -
1. a kernel module
2. a shared library
3. 2 demo binaries
Their top-level makefile builds everything. From Yocto's perspective, it
interfaces with this code as though the whole thing is a kernel module. There
may be adversed implication to the shared library if I were to use the
KERNEL_CC variable. So, I'm thinking of modifying the 3rd party makefile to
support separate builds.
What documentation/section I should look into for patching the makefile
(minimize changes to original vendor files)?
Thanks,
Raymond
From: Anuj Mittal
Sent: Thursday, April 5, 2018 11:39 PM
To: Raymond Yeung; yocto@yoctoproject.org
Subject: Re: [yocto] Adding debug output in recipe
On 04/06/2018 02:05 PM, Raymond Yeung wrote:
> Hi Anuj,
>
>
> "bitbake -e" is very useful for debugging out-of-tree build issue.
> However, looks like I have another issue. From "devtool build" output,
> I could see variables passed into makefile. Let's focus on "CC" for now:
>
>
> CC=x86_64-poky-linux-gcc -fuse-ld=bfd
I think that is the value of KERNEL_CC if you're inheriting module.bbclass.
>
>
> If we compare this to "bitbake -e" dump:
>
>
> export CC="x86_64-poky-linux-gcc -m64 -march=corei7 -mtune=corei7
> -mfpmath=sse -msse4.2
> --sysroot=/a/ryeung/dev/yocto-git/yocto_build/build/tmp/sysroots/intel-corei7-64"
>
>
> You can see somehow the variable is modified. Let's focus on --sysroot
> portion. Without it, there seems to be no way for me to control
> LIBRARY_PATH's value. The result is that the linker couldn't find
> crti.o and a few other files. By manually adding back --sysroot
> portion, I could now get past this failure, onto the next.
>
>
> I suppose, as a possible final solution, I could do:
>
>
> $(CC) --sysroot=$(KERNEL_SRC) ...
This looks like a problem with your source Makefile. Please check the
variable that points to kernel sources in your Makefile.
Use EXTRA_OEMAKE += "='${STAGING_KERNEL_DIR}'" if the variable
name used in your Makefile is different from KERNEL_PATH or KERNEL_SRC.
You can also check run.do_compile file to see the exact compile steps.
Please see:
https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules
Yocto Project Linux Kernel Development
Manual
www.yoctoproject.org
Kernel modification involves changing the Yocto Project kernel, which could
involve changing configuration options as well as adding new kernel recipes.
>
>
> I'm really looking for simpler, more intuitive solution. What about the
> missing "-m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2" in the
> export?
>
>
> Raymond
>
>
>
>
>
> *From:* Anuj Mittal
> *Sent:* Thursday, April 5, 2018 9:52 PM
> *To:* Raymond Yeung; yocto@yoctoproject.org
> *Subject:* Re: [yocto] Adding debug output in recipe
>
> On 04/05/2018 03:33 PM, Raymond Yeung wrote:
>> Is there a way to add simple debug output (ideally don't need to control
>> debug level) to echo out values of variables? I tried the bb.xxx
>> variants, but couldn't get them to work.
>>
>
> To find out what a variable is being set to, you can try:
>
> bitbake -e
>
> Please see:
>
> https://wiki.yoctoproject.org/wiki/Technical_FAQ#I_set_a_variable_but_it_doesn.27t_seem_to_be_having_an_effect.2C_how_do_I_fix_this.3F
>
> Is that what you were looking for?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding support for GPIO chipset, Am I doing it right ?
Hi, I'm using poky Rocko. I'm building a linux-rt based system (I'm using bitbake image-core-rt). The GPIO chip (Fintek F81866d) is not supported by the kernel we selected (4.4). I downloaded the patch which adds support of Fintek F81866d to kernel (from https://patchwork.ozlabs.org/patch/566380/) and add the patch to my kernel linux recipes (via SRC_URI +=) When building the image, the kernel is being recompiled but the patch is not applied (I still get an error message saying that the chip is not supported when I try to modprobe the module). Is this way of adding support of the Fintek F81866d to the kernel is the right way ? How can I check that the patch is applied ? Thanks Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-virtualization -> docker not packaged when using PACKAGE_CLASSES ?= "package_deb"
Hello, I encountered a funny behavior the other day. While trying to integrate Docker into my image using the openembedded meta-virtualization layer, I happened to not being able to get my image finalized. Usually I build with PACKAGE_CLASSES ?= "package_deb". I also added DISTRO_FEATURES_append = " virtualization" The build process aborts at some point within do_rootfs, stating something like that the package 'docker' could not be found. I tracked down the problem to docker's build/tmp/work//docker//deploy-debs/ directory. I found the following packages: docker-contrib_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_amd64.deb docker-distribution-dev_v2.6.2-r0_amd64.deb docker-registry_v2.6.2-r0_amd64.deb docker-dbg_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_amd64.deb docker-distribution-ptest_v2.6.2-r0_amd64.deb docker-distribution-dbg_v2.6.2-r0_amd64.deb docker-ptest_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_amd64.deb The package that is actually missing, is the docker package itself. I suppose it would be named docker_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_amd64.deb. There is not any single warning or error thrown whatsoever during the build of docker, it seems to just silently refusing to build the package. Yet, when change PACKAGE_CLASSES ?= "package_deb" to PACKAGE_CLASSES ?= "package_rpm" it would build all required docker RPM-Packages just fine. At the end of the day I way able to get a complete image with Docker integrated, which is fine for the moment. Unfortunately I need to stick with the DEB format for update reasons, so eventually I need to deal with this issue again. Has anyone seen this happening as well? Any idea, where and how to fix this? Thanks in advance for your help! Mark -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] adding avocado to custom image
Hello everyone, I'm trying to install a python package and its additional plugins to my custom image. These plugins are stored in a directory within the package's folder named optional_plugins. Plugins can easily be installed using the command python setup.py install from within the plugin folder. I successfully installed the main package using a custom recipe and luckily it works fine on the built image. Unfortunately, none of the optional_plugins I tried to install, are instead available on the image. My question is, how am I supposed to install these plugins from my recipe considering that they need to be installed running python setup.py install? I am quite new to yocto, any suggestion is appreciated. Thanks. Frank. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] bitbake failed during build of openjdk-8 using meta-linaro aarm64
Hi,
I'm building the openjdk-8 from (openjdk-8_0.1.bb) linaro aarm64. But actually
the build failed. I saw similar problem last year but there was no solution to
that . Is this build working at all ?
WARNING: mpfr-native-3.1.5-r0 do_fetch: Failed to fetch URL
http://www.mpfr.org/mpfr-3.1.5/mpfr-3.1.5.tar.xz, attempting MIRRORS if
available
WARNING: libmpc-native-1.0.3-r0 do_fetch: Failed to fetch URL
http://www.multiprecision.org/mpc/download/mpc-1.0.3.tar.gz, attempting MIRRORS
if available
WARNING: libpng-native-1.6.28-r0 do_fetch: Failed to fetch URL
http://distfiles.gentoo.org/distfiles/libpng-1.6.28.tar.xz, attempting MIRRORS
if available
ERROR: openjdk-8-jre-0.1-r16.0 do_fetch: Error executing a python function in
exec_python_func() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
0001:
*** 0002:base_do_fetch(d)
0003:
File:
'/home/marszc/.../.../build-rpb/conf/../../layers/openembedded-core/meta/classes/base.bbclass',
lineno: 153, function: base_do_fetch
0149:if len(src_uri) == 0:
0150:return
0151:
0152:try:
*** 0153:fetcher = bb.fetch2.Fetch(src_uri, d)
0154:fetcher.download()
0155:except bb.fetch2.BBFetchException as e:
0156:bb.fatal(str(e))
0157:}
File: '/home/marszc/.../bitbake/lib/bb/fetch2/__init__.py', lineno: 1565,
function: __init__
1561:
1562:for url in urls:
1563:if url not in self.ud:
1564:try:
*** 1565:self.ud[url] = FetchData(url, d, localonly)
1566:except NonLocalMethod:
1567:if localonly:
1568:self.ud[url] = None
1569:pass
File: '/home/marszc/.../bitbake/lib/bb/fetch2/__init__.py', lineno: 1244,
function: __init__
1240:logger.warning('Consider updating %s recipe to use
"protocol" not "proto" in SRC_URI.', d.getVar('PN'))
1241:self.parm["protocol"] = self.parm.get("proto", None)
1242:
1243:if hasattr(self.method, "urldata_init"):
*** 1244:self.method.urldata_init(self, d)
1245:
1246:if "localpath" in self.parm:
1247:# if user sets localpath for file, use it instead.
1248:self.localpath = self.parm["localpath"]
File: '/home/marszc/.../bitbake/lib/bb/fetch2/hg.py', lineno: 69, function:
urldata_init
0065:ud.proto = 'file'
0066:else:
0067:ud.proto = "hg"
0068:
*** 0069:ud.setup_revisions(d)
0070:
0071:if 'rev' in ud.parm:
0072:ud.revision = ud.parm['rev']
0073:elif not ud.revision:
File: '/home/marszc/.../bitbake/lib/bb/fetch2/__init__.py', lineno: 1274,
function: setup_revisions
1270:
1271:def setup_revisions(self, d):
1272:self.revisions = {}
1273:for name in self.names:
*** 1274:self.revisions[name] = srcrev_internal_helper(self, d,
name)
1275:
1276:# add compatibility code for non name specified case
1277:if len(self.names) == 1:
1278:self.revision = self.revisions[self.names[0]]
File: '/home/marszc/.../bitbake/lib/bb/fetch2/__init__.py', lineno: 1139,
function: srcrev_internal_helper
1135:
1136:if srcrev == "INVALID" or not srcrev:
1137:raise FetchError("Please set a valid SRCREV for url %s
(possible key names are %s, or use a ;rev=X URL parameter)" % (str(attempts),
ud.url), ud.url)
1138:if srcrev == "AUTOINC":
*** 1139:srcrev = ud.method.latest_revision(ud, d, name)
1140:
1141:return srcrev
1142:
1143:def get_checksum_file_list(d):
File: '/home/marszc/.../bitbake/lib/bb/fetch2/__init__.py', lineno: 1530,
function: latest_revision
1526:if not hasattr(self, "_latest_revision"):
1527:raise ParameterError("The fetcher for this URL does not
support _latest_revision", url)
1528:
1529:revs = bb.persist_data.persist('BB_URI_HEADREVS', d)
*** 1530:key = self.generate_revision_key(ud, d, name)
1531:try:
1532:return revs[key]
1533:except KeyError:
1534:revs[key] = rev = self._latest_revision(ud, d, name)
File: '/home/marszc/.../bitbake/lib/bb/fetch2/__init__.py', lineno: 1542,
function: generate_revision_key
1538:latest_rev = self._build_revision(ud, d, name)
1539:return True, str(latest_rev)
1540:
1541:def generate_revision_key(self, ud, d, name):
*** 1542:key = self._revision_key(ud, d, name)
1543:return "%s-%s" % (key, d.getVar(
[yocto] [meta-gplv2][PATCH] layer.conf: add LAYERSERIES_COMPAT
Signed-off-by: Martin Jansa --- conf/layer.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index f5601bb..3d614dc 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -13,3 +13,5 @@ BBFILE_PRIORITY_gplv2 = "1" LAYERVERSION_gplv2 = "1" LAYERDEPENDS_gplv2 = "core" + +LAYERSERIES_COMPAT_gplv2 = "sumo" -- 2.15.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem with packages during "devtool build"
Hi Robert, I'd already read the out-of-tree example; it's the first thing I checked. After some changes in 3rd party Makefile, I'm running into errors in do_compile step. My new question now is, how the Makefile picks up cross-compile INC path, as well as the LINKER path. The variable KERNEL_SRC isn't enough to provide the needed clues for the above. And it'd be a bad idea to hardcode paths in 3rd party code. Is there an easy way to have devtool pass in more variables? And what variables should we use? Raymond From: Robert Berger Sent: Thursday, April 5, 2018 11:48 AM To: Raymond Yeung Cc: Khem Raj; yocto@yoctoproject.org Subject: Re: [yocto] Problem with packages during "devtool build" Hi, On 2018-04-05 21:02, Raymond Yeung wrote: > "inherit module" is already in recipes/cgosapi.bb file. In fact, as I > use devtool to "add" the recipe to workspace layer, this .bb file is > autogenerated. I only added the last line that sets KERNELDIR that 3rd > Party software's Makefile uses. Did you have a look at this out of tree kernel module example? https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod You might want to use this makefile and add your stuff there. Regards, Robert -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] glib-initial do_install fails at 'oe_runmake csu/subdir_lib' (Rocko)
Hello,
I cannot buid core-image-minimal for a imx25pdk machine (rocko).
Building stops at glibc-initial install.
Building for another machine with morty (imx25pdk is not available in
morty) works.
I assume is related to this part of the recipe (glibc-initial.inc):
do_install () {
**
oe_runmake csu/subdir_lib
mkdir -p ${D}${libdir}/
install -m 644 csu/crt[1in].o ${D}${libdir}
**
}
Host machine is an Ubuntu 16.04...
Linux vpalacio-laptop 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12
21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Googling for the issue, I've found this post that looks like the same
issue: https://lists.yoctoproject.org/pipermail/yocto/2015-May/025018.html
Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-fsl-linux-gnueabi"
MACHINE = "imx25pdk"
DISTRO = "fsl-x11"
DISTRO_VERSION = "2.4"
TUNE_FEATURES = "arm armv5 thumb dsp"
TARGET_FPU = "soft"
meta
meta-poky = "HEAD:fdeecc901196bbccd7c5b1ea4268a2cf56764a62"
meta-oe
meta-multimedia = "HEAD:dacfa2b1920e285531bec55cd2f08743390aaf57"
meta-freescale = "HEAD:d6141ea291a1ac9ab8fb1dd1110d408f840fda57"
meta-freescale-3rdparty = "HEAD:62de01743c9233ea718de22991c47b73a78b4857"
meta-freescale-distro = "HEAD:0ec6d7e206705702b5b534611754de0787f92b72"
*+
| NOTE: make PARALLELMFLAGS=-j 4 SHELL=/bin/bash csu/subdir_lib
| make -r PARALLELMFLAGS="-j 4" -C ../git objdir=`pwd` csu/subdir_lib
| make[1]: Entering directory
'/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/git'
| make -j 4 subdir=csu -C csu ..=../ subdir_lib
| make[2]: Entering directory
'/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/git/csu'
| /bin/bash ../scripts/gen-libc-abis \
| arm-fsl-linux-gnueabi \
| < ../libc-abis >
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/libc-abis.hT
| LC_ALL=C gawk -f ../scripts/abi-versions.awk
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/Versions.all
>
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/abi-versions.hT
| gawk -f ../scripts/gen-tunables.awk ../elf/dl-tunables.list >
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/dl-tunable-list.T
| .././scripts/mkinstalldirs
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/csu
| mv -f
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/abi-versions.hT
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/abi-versions.h
| /bin/bash ../scripts/move-if-change
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/libc-abis.hT
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/libc-abis.h
| ../Makeconfig:1137: recipe for target
'/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/dl-tunable-list.stmp'
failed
| make[2]: ***
[/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/dl-tunable-list.stmp]
Error 1
| mkdir -p --
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/csu
| make[2]: *** Waiting for unfinished jobs
| (files="../crypt/Banner ../libidn/Banner ../nptl/Banner
../resolv/Banner"; \
| if test -n "$files"; then \
| printf '"Available extensions:\\n"\n'; \
| sed -e '/^#/d' -e 's/^[[:space:]]*/ /' \
| -e 's/^\(.*\)$/\"\1\\n\"/' $files; \
| fi) >
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/csu/version-info.hT
| mv -f
/media/vpalacio/LINUX_DEV/fsl-community-bsp-mx25pdk/build/tmp/work/armv5e-fsl-linux-gnueabi/glibc-initial/2.26-r0/build-arm-fsl-linux-gnueabi/csu/version-inf
[yocto] FW: [meta-qt5]Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed.
I'm so sorry the error message is "Feature 'tslib' was enabled, but the pre-condition 'libs.tslib' failed.", not disabled. So sorry for confusing. :( Koo. From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of dhkoo Sent: Friday, April 06, 2018 4:52 PM To: yocto@yoctoproject.org Subject: [yocto] [meta-qt5]Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed. Hello. I want to compile the tslib enabled Qt5.10 on the yocto. After running "bitbake core-image-mymachine", on the log 'run.do_configure' shows me "-no-tslib" option configured. So I modified qtbase_git.bb to enable "-tslib" option. And after that, bitbake shows me "Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed." I added tslib, and xf86-input-tslib at "packagegroup.bb" and using architecture based on arm7a. Is there any good idea for enable "tslib" successfully? regards. Koo. -- ___ 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] [meta-qt5]Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed.
Hello. I want to compile the tslib enabled Qt5.10 on the yocto. After running "bitbake core-image-mymachine", on the log 'run.do_configure' shows me "-no-tslib" option configured. So I modified qtbase_git.bb to enable "-tslib" option. And after that, bitbake shows me "Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed." I added tslib, and xf86-input-tslib at "packagegroup.bb" and using architecture based on arm7a. Is there any good idea for enable "tslib" successfully? regards. Koo. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
