From: Martin Jansa <martin.jansa@gmail.com>
To: ZHOU Yanxin <y.zhou@staubli.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: fsl-community-bsp + meta-qt5
Date: Thu, 21 Apr 2016 13:08:19 +0200 [thread overview]
Message-ID: <20160421110819.GA2240@jama> (raw)
In-Reply-To: <0495a539e9944301a10365a96225ad2a@FAV151WIN.staubli.pri>
[-- Attachment #1: Type: text/plain, Size: 2403 bytes --]
On Thu, Apr 21, 2016 at 02:46:29AM +0000, ZHOU Yanxin wrote:
> Dear Martin,
Hi Zhou,
> I have built the cross toolchain for qt5 and the rootfs using: bitbake meta-toolchain-qt5 and bitbake fsl-image-multimedia-full.
> Fsl-community-bsp and meta-qt5 both use Jethro branch.
Use ML for generic questions like this. I'm not actively using FSL
> Following are some of my questions:
>
>
> 1. In the rootfs which I put in the "riotboard", is qt5 library already in it? Do I need to compile the source of qt5 and copy it to the board
>
> Separately?
I don't know what fsl-image-multimedia-full image contains, but you
probably need to add it to the image like any other packages.
> 2. I have set up the qtcreator: device, kit, qt version, compiler, debugger, also ssh connection, but when I run the application, qt says
>
> "This application failed to start because it could not find or load the qt platform plugin xcb, available platform plugin are: eglfs, minimal, minimalegl, offscreen".
Have you tried to set the correct platform?
> 3. In the Jethro branch of meta-qt5, the qtbase.inc is missing, correct? I found on the internet, that I can modify the PACKAGECONFIG[gles] value, add -qpa eglfs.
qtbase.inc was integrated into qtbase_git.bb.
> 4. I also found that in the Jethro branch, the serialport is also missing, but in our application, we need this function to handle the serial keyboard.
Why you think it's missing? I see it there.
> Looking forward to your reply.
>
> Best regards!
>
> Yanxin ZHOU
> Electronic Product Engineering
> STAUBLI HANGZHOU LTD.
> No 123 Weiken Street Hangzhou Economic & Technological Development Zone
> 310018 Hangzhou / CN
> Phone: +86 40066 70066
> Mobile: +86 18605811677
> mailto: y.zhou@staubli.com<mailto:y.zhou@staubli.com>
> www.staubli.com<http://www.staubli.com>
> This e-mail and any attachment (the 'message') are confidential and privileged and intended solely for the person or the entity
> to which it is addressed. If you have received it in error, please advise the sender by return e-mail and delete it immediately.
> Any use not in accordance with its purpose, any dissemination or reproduction, either whole or partial, by entities other than
> the intended recipient is strictly prohibited.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
parent reply other threads:[~2016-04-21 11:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0495a539e9944301a10365a96225ad2a@FAV151WIN.staubli.pri>]
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=20160421110819.GA2240@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=y.zhou@staubli.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox