From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to build the qt plugin in gst1-plugins-bad ?
Date: Wed, 19 Jul 2017 12:01:13 +0200 [thread overview]
Message-ID: <20170719120113.62df8762@windsurf> (raw)
In-Reply-To: <CADujc4o_1XZLQymNx3fQk5n9FOhg=9xNKw5U2GPSsGBCxHyhSA@mail.gmail.com>
Hello,
On Wed, 19 Jul 2017 17:55:54 +0800, Glenn Coombs wrote:
> Thanks for the debug. Is that section with HAVE_WINDOW_VIV_FB from the
> build/gst1-plugins-bad-1.10.4/configure.ac file? I have this section in
> that file at line 1059:
>
> if test "x$NEED_EGL" != "xno"; then
> if test "x$HAVE_WINDOW_WAYLAND" = "xyes" -o "x$HAVE_WINDOW_X11" =
> "xyes" -o "x$HAVE_WINDOW_DISPMANX" = "xyes"; then
> GL_LIBS="$GL_LIBS -lEGL $EGL_LIBS"
> GL_CFLAGS="$GL_CFLAGS $EGL_CFLAGS"
> USE_EGL=yes
> fi
> fi
>
> As you can see I am missing the HAVE_WINDOW_VIV_FB bit. Looking at the
> output of dmesg on my target system I can see this version: Buildroot
> 2017.05-00055-g338f004. Presumably I need an even newer version of
> buildroot than I already have ?
gst1-plugins-bad has been upgraded in commit
38e95aa170360850d68459516965b98cc15f3f49, which is *after* the commit
you're currently based on. Your commit is 55 commits after 2017.05,
while the gst1-plugins-bad has been done 807 commits after 2017.05.
So yes: update your Buildroot to the latest master! :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-19 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 9:17 [Buildroot] How to build the qt plugin in gst1-plugins-bad ? Glenn Coombs
2017-07-19 9:35 ` Thomas Petazzoni
2017-07-19 9:55 ` Glenn Coombs
2017-07-19 10:01 ` Thomas Petazzoni [this message]
2017-07-21 7:39 ` Glenn Coombs
2017-07-21 7:44 ` Thomas Petazzoni
2017-07-21 8:35 ` Glenn Coombs
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=20170719120113.62df8762@windsurf \
--to=thomas.petazzoni@free-electrons.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.