From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] raspberry pi, Qt5 and audio output
Date: Fri, 28 Feb 2014 08:57:29 +0100 [thread overview]
Message-ID: <53104169.90506@gmail.com> (raw)
Hello,
with buildroot Buildroot 2014.02-rc3-00017-g29e5833 and the attached
.config file I'm able to run Qt5 + webkit application on the RPi.
Still I cannot execute any audio file using Qt5 Multimedia.
I get a warning like this:
defaultServiceProvider::requestService(): no service found for -
"org.qt-project.qt.mediaplayer"
Anyway I can play any file using aplay, or other players.
Perhaps I miss some qt-related stuff... did someone run into the same
problem?
Thanks!
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 49706 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140228/b6a084b9/attachment.wsdl>
next reply other threads:[~2014-02-28 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 7:57 Marco Trapanese [this message]
2014-03-04 7:43 ` [Buildroot] raspberry pi, Qt5 and audio output Marco Trapanese
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=53104169.90506@gmail.com \
--to=marcotrapanese@gmail.com \
--cc=buildroot@busybox.net \
/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