From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: meta-freescale@yoctoproject.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: QtMultimedia on i.MX6
Date: Mon, 08 Jul 2013 09:08:29 +0200 [thread overview]
Message-ID: <1792815.4kkagN4gBy@rudolf> (raw)
In-Reply-To: <51D84F43.50700@boundarydevices.com>
On Saturday, 06 July, 2013 10:09:23 Eric Nelson wrote:
> On 07/06/2013 06:09 AM, Otavio Salvador wrote:
> > On Fri, Jul 5, 2013 at 10:52 PM, Trevor Woerner
> >
> > <trevor.woerner@linaro.org> wrote:
> >> On 5 July 2013 19:04, Eric Nelson <eric.nelson@boundarydevices.com>
wrote:
> >>> I'm interested in the details of how you added Qt5 to your
> >>> build. Qt4 seems to be directly accessible in Yocto, but not Qt5.
> >>
> >> I'm guessing/hoping the meta-qt5 layer was used?
> >> http://layers.openembedded.org/layerindex/layer/meta-qt5/
Nop sorry :)
I'm building out-side of yocto using configure/make/... directly.
It's simpler for me as I'm doing that for a couple of years now and I have the
full environment under control (/I know what I'm doing).
... at least for development.
> >
> > Yes and if you use master-next you win a qt5 binding for mx6 as well.
> > I hope to finish testing it and looking at X11 this week so we merge
> > it in master.
>
> Many thanks!
I got a step further. I got gstreamer also running within QtMultimedia, but
using glimagesink seems to be wrong (it still renders directly to framebuffer
which is not what I wanted in the end), but 'glupload' sounds very promising,
just need to get all the puzzle pieces into the right order :)
So there is still some work to do, but I think I know what to do.
I keep you guys posted.
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
prev parent reply other threads:[~2013-07-08 7:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 15:03 QtMultimedia on i.MX6 Thomas Senyk
2013-07-04 15:14 ` Thomas Senyk
2013-07-04 21:42 ` Otavio Salvador
2013-07-04 21:53 ` Sébastien Taylor
2013-07-04 22:03 ` Otavio Salvador
2013-07-05 17:16 ` Rogerio Nunes
2013-07-09 8:14 ` Thomas Senyk
2013-07-09 11:26 ` Otavio Salvador
2013-07-09 23:53 ` Rogerio Nunes
2013-07-10 0:25 ` Philip Craig
2013-07-10 8:26 ` Thomas Senyk
2013-07-10 9:13 ` Philip Craig
2013-07-10 9:52 ` Thomas Senyk
2013-07-10 10:32 ` Philip Craig
2013-07-10 10:41 ` Thomas Senyk
2013-07-10 13:30 ` Philip Craig
2013-07-11 19:58 ` Robert Winkler
2013-07-12 8:56 ` Thomas Senyk
2013-07-15 18:18 ` Robert Winkler
2013-07-16 8:15 ` Thomas Senyk
2013-07-05 23:04 ` Eric Nelson
2013-07-06 1:52 ` Trevor Woerner
2013-07-06 13:09 ` Otavio Salvador
2013-07-06 17:09 ` Eric Nelson
2013-07-08 7:08 ` Thomas Senyk [this message]
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=1792815.4kkagN4gBy@rudolf \
--to=thomas.senyk@pelagicore.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.