From: Laurent JOLI <laurent.joli@kapelse.com>
To: TEXIER Pierre-Jean <texier.pj2@gmail.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Add lib to meta-qt5
Date: Fri, 23 Mar 2018 16:09:51 +0100 (CET) [thread overview]
Message-ID: <1490723767.9894976.1521817791424.JavaMail.zimbra@kapelse.com> (raw)
In-Reply-To: <CALRtUqvUHaaEf-jOWmFHzotarYtOBrV0ZZf6kS8fgFaCNeM4AQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6781 bytes --]
De: "TEXIER Pierre-Jean" <texier.pj2@gmail.com>
À: "Laurent JOLI" <laurent.joli@kapelse.com>
Cc: "yocto" <yocto@yoctoproject.org>
Envoyé: Vendredi 23 Mars 2018 15:20:50
Objet: Re: [yocto] Add lib to meta-qt5
Hi Laurent,
The SDK is defined by the following packagegroup:
[ https://github.com/meta-qt5/meta-qt5/blob/jethro/recipes-qt/packagegroups/packagegroup-qt5-toolchain-target.bb | https://github.com/meta-qt5/meta-qt5/blob/jethro/recipes-qt/packagegroups/packagegroup-qt5-toolchain-target.bb ] .
I build all my SDK with :
bitbake -v meta-toolchain-qt5
At the end I have a big script :
.-(/media/tmp-jethro-XXX/deploy/sdk)--------
`--> lc
total 824M
-rw-r--r-- 1 ljoli ljoli 8,9K mars 23 13:28 pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.host.manifest
-rwxr-xr-x 1 ljoli ljoli 824M mars 23 13:29 pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.sh
-rw-r--r-- 1 ljoli ljoli 19K mars 23 13:28 pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest
But I have not my lib of libqt5declarative :
`--> cat * | grep -ri libqt5
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-dbg core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-dev core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-examples-dbg core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-mkspecs core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-plugins core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-plugins-dbg core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-qmlplugins core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors-qmlplugins-dbg core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5sensors5 core2-32 5.5.1+git0+6a16281ace
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5serialport-dbg core2-32 5.5.1+git0+ad108e9d56
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5serialport-dev core2-32 5.5.1+git0+ad108e9d56
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5serialport-mkspecs core2-32 5.5.1+git0+ad108e9d56
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5serialport5 core2-32 5.5.1+git0+ad108e9d56
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5svg-dbg core2-32 5.5.1+git0+b5d689eaaf
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5svg-dev core2-32 5.5.1+git0+b5d689eaaf
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5svg-mkspecs core2-32 5.5.1+git0+b5d689eaaf
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5svg-plugins core2-32 5.5.1+git0+b5d689eaaf
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5svg-plugins-dbg core2-32 5.5.1+git0+b5d689eaaf
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5svg5 core2-32 5.5.1+git0+b5d689eaaf
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5webchannel-dbg core2-32 5.5.1+git0+906d910415
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5webchannel-dev core2-32 5.5.1+git0+906d910415
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5webchannel-mkspecs core2-32 5.5.1+git0+906d910415
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5webchannel-qmlplugins core2-32 5.5.1+git0+906d910415
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5webchannel-qmlplugins-dbg core2-32 5.5.1+git0+906d910415
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5webchannel5 core2-32 5.5.1+git0+906d910415
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5websockets-dbg core2-32 5.5.1+git0+08582917b4
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5websockets-dev core2-32 5.5.1+git0+08582917b4
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5websockets-mkspecs core2-32 5.5.1+git0+08582917b4
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5websockets-qmlplugins core2-32 5.5.1+git0+08582917b4
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5websockets-qmlplugins-dbg core2-32 5.5.1+git0+08582917b4
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5websockets5 core2-32 5.5.1+git0+08582917b4
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5xmlpatterns-dbg core2-32 5.5.1+git0+3338de7bbe
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5xmlpatterns-dev core2-32 5.5.1+git0+3338de7bbe
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5xmlpatterns-mkspecs core2-32 5.5.1+git0+3338de7bbe
pokykapsofia-glibc-i686-meta-toolchain-qt5-core2-32-toolchain-1.0.target.manifest:libqt5xmlpatterns5 core2-32 5.5.1+git0+3338de7bbe
---
Pierre-Jean
2018-03-23 14:39 GMT+01:00 Laurent JOLI < [ mailto:laurent.joli@kapelse.com | laurent.joli@kapelse.com ] > :
Hello,
I'm working with an old version of YOCTO, jethro 2.0.
And I want to produce an SDK of QT5, version 5.5.1.
So, I add the layer meta-qt5 on YOCTO for build the following recipe :
[ https://github.com/meta-qt5/meta-qt5/tree/jethro | https://github.com/meta-qt5/meta-qt5/tree/jethro ]
meta-toolchain-qt5
My question is :
How to add an lib ( libqt5declarative.so.5.5.1 for example ) on SDK of QT5 ?
thanks by advance.
--
_______________________________________________
yocto mailing list
[ mailto:yocto@yoctoproject.org | yocto@yoctoproject.org ]
[ https://lists.yoctoproject.org/listinfo/yocto | https://lists.yoctoproject.org/listinfo/yocto ]
[-- Attachment #2: Type: text/html, Size: 8545 bytes --]
next prev parent reply other threads:[~2018-03-23 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7.1521745201.12814.yocto@yoctoproject.org>
2018-03-23 13:39 ` Add lib to meta-qt5 Laurent JOLI
2018-03-23 14:20 ` TEXIER Pierre-Jean
2018-03-23 15:09 ` Laurent JOLI [this message]
2018-03-23 16:09 ` TEXIER Pierre-Jean
2018-03-23 16:52 ` Laurent JOLI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490723767.9894976.1521817791424.JavaMail.zimbra@kapelse.com \
--to=laurent.joli@kapelse.com \
--cc=texier.pj2@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.