Openembedded Core Discussions
 help / color / mirror / Atom feed
From: alexander.kanavin@linux.intel.com
To: "Alex M" <0xf777@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Phonon is not available Qt 4.8.7
Date: Thu, 20 Aug 2015 19:20:10 +0300 (EEST)	[thread overview]
Message-ID: <53995.10.252.47.114.1440087610.squirrel@linux.intel.com> (raw)
In-Reply-To: <CAHyyKNnpUqqsDahww8wCKbDCrFSS8Ry7cdnpmTYXx0ipgxx0JA@mail.gmail.com>

> Hello!
> I have a piece of my custom software which is depends on Qt4 + Phonon +
> gstreamer 0.1 and two years ago I had successfully built oe-core image.
> Recent version of oe-core (19 Aug 2015) contain QT_PHONON ?= "-no-phonon"
> option inside qt4.inc file. Why this option banned in default Qt 4
> configuration? Also I do not see qt4-plugin-phonon-backend-gstreamer
> package in recent version, which my software also requires. Other
> gstreamer-0.1 components is fine and already built. What I should do to
> activate Phonon support for Qt4 in oe-core?

The reasons for this are explained here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6294

In the short term, don't use the master branch of oe-core. Use the current
stable branch (fido) which should still have the Qt4 with Phonon enabled.
It's also possible to use the master branch, by creating a custom layer
with a .bbappend file that tweaks the Qt4 build options, but I think it's
less hassle to roll back to fido.

In the long term, do port your software to Qt5. Qt4 itself goes out of
support at the end of 2015, and we plan to move it out of oe-core around
same time.

Alex


      parent reply	other threads:[~2015-08-20 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 14:18 Phonon is not available Qt 4.8.7 Alex M
2015-08-20 14:54 ` Martin Jansa
2015-08-20 16:20 ` alexander.kanavin [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=53995.10.252.47.114.1440087610.squirrel@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=0xf777@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox