From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qt5base: add optional gstreamer1 support
Date: Thu, 22 Oct 2015 19:49:21 +0200 [thread overview]
Message-ID: <877fmelroe.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <0874644c-9a80-4da8-af8d-ea8cad036c35@MAIL-SINTERS-01.sinters-int.fr> (Julien CORJON's message of "Thu, 22 Oct 2015 15:19:08 +0000")
>>>>> "Julien" == Julien CORJON <corjon.j@ecagroup.com> writes:
Hi,
>> So I've marked is as superseeded.
>>
>> And 504627 looks pretty much like my patch except that it adds gstreamer
>> 0.10 support which I think we shouldn't do (as qt5multimedia doesn't
>> build with it).
> Qt-5.5.0 announce support[1] for both gstreamer-0.10 & gstreamer-1.0.
> Also note that gstreamer-0.10 is still the Qt default version in case
> both are present.
Yes, but E.G. the gstreamer 0.10 support in qt5multimedia doesn't build,
whereas the 1.x support does, and we prefer 1.x over 0.10 elsewhere in
Buildroot.
>>
>> Once my patch is a applied I'll mark 504627 as superseeded. I wasn't
>> able to reproduce the pkg-config issue you mentioned.
> You probably missed that qt5base use host pkg-config to detect gstreamer
> version. As autobuild chroot environment have neither of them they both
> fail at qt5multimedia install time.
Ok, but gstreamer1 pulls in host-pkgconf, so it should be available when
qt5base runs the configure step, right?
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2015-10-22 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:06 [Buildroot] [PATCH 1/2] qt5base: add optional gstreamer1 support Peter Korsgaard
2015-10-21 8:06 ` [Buildroot] [PATCH 2/2] qt5multimedia: drop broken gstreamer 0.10 support Peter Korsgaard
2015-10-25 20:03 ` Peter Korsgaard
2015-10-21 11:42 ` [Buildroot] [PATCH 1/2] qt5base: add optional gstreamer1 support Thomas Petazzoni
2015-10-21 11:48 ` Peter Korsgaard
2015-10-22 15:19 ` Julien CORJON
2015-10-22 17:49 ` Peter Korsgaard [this message]
2015-10-22 18:59 ` Will Wagner
2015-10-22 20:17 ` Peter Korsgaard
2015-10-23 7:55 ` Will Wagner
2015-10-25 20:02 ` Peter Korsgaard
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=877fmelroe.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.