Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qt/qt5base: force gstreamer on configure
Date: Tue, 15 Sep 2015 09:37:15 +0100	[thread overview]
Message-ID: <55F7D8BB.9040301@carallon.com> (raw)
In-Reply-To: <20150808151617.2f10d4b3@free-electrons.com>

On 08/08/2015 14:16, Thomas Petazzoni wrote:
> Dear Julien Corjon,
>
> On Thu,  6 Aug 2015 12:06:14 +0200, Julien Corjon wrote:
>> Fixes: http://autobuild.buildroot.net/results/0ee0f879e8563954c64b3940cdec39d2e6de937a/
>>
>> Signed-off-by: Julien Corjon <corjon.j@ecagroup.com>
>> ---
>>   package/qt5/qt5base/qt5base.mk | 10 ++++++++++
>>   1 file changed, 10 insertions(+)
>
> I'm sorry, but I don't think this is really the source of the problem.
> I did reproduce this build failure, and even if GStreamer is built
> before Qt5 (which is the case in the build failure you're linking in
> the commit log), Qt5 concludes that GStreamer is not available.
>
> And this is because for some reason, Qt5 now seems to ignore the
> PKG_CONFIG environment variable that we pass to it. I've added some
> debugging messages to the packagesExist() function, and it uses just
> "pkg-config" (i.e the system pkg-config, not the one built and
> installed by Buildroot in $(HOST_DIR)/usr/bin).
>
> While I think that your patch should be applied (it's good to make
> optional dependencies explicit), I also think the pkg-config problem
> should be investigated and fixed.
>

I have just been testing 2015.08 and have immediately hit exactly the 
same issue. I have done some digging into qt5 and I think I see the 
issue. The problem is that qmake never looks at environment variables, 
only things passed on the command line. The patch below fixes the issue 
for me by explicitly passing PKG_CONFIG on the command line. What is 
unclear is why I am suddenly seeing the issue in 5.5.0 but not 5.4.1 as 
that bit of code seems the same in both versions.

I'll report the issue upstream and see what they say.

Should I spin this into a patch?

--- qt5base-5.5.0/config.tests/unix/compile.test.orig	2015-09-15 
08:53:45.202320408 +0100
+++ qt5base-5.5.0/config.tests/unix/compile.test	2015-09-15 
08:54:02.720770491 +0100
@@ -67,7 +67,7 @@ test -r Makefile && $MAKE distclean >/de
  # Make sure output from possible previous tests is gone
  rm -f "$EXE" "${EXE}.exe"

-set -- "$OUTDIR/bin/qmake" -nocache -spec "$QMKSPEC" 
"CONFIG+=$QMAKE_CONFIG" "CONFIG+=android_app" "CONFIG-=debug_and_release 
app_bundle lib_bundle" "LIBS*=$LFLAGS" "LIBS+=$MAC_ARCH_LFLAGS" 
"INCLUDEPATH*=$INCLUDEPATH" "QMAKE_CXXFLAGS*=$CXXFLAGS" 
"QMAKE_CXXFLAGS+=$MAC_ARCH_CXXFLAGS" "$SRCDIR/$TEST/$EXE.pro" -o 
"$OUTDIR/$TEST/Makefile"
+set -- "$OUTDIR/bin/qmake" "PKG_CONFIG=$PKG_CONFIG" -nocache -spec 
"$QMKSPEC" "CONFIG+=$QMAKE_CONFIG" "CONFIG+=android_app" 
"CONFIG-=debug_and_release app_bundle lib_bundle" "LIBS*=$LFLAGS" 
"LIBS+=$MAC_ARCH_LFLAGS" "INCLUDEPATH*=$INCLUDEPATH" 
"QMAKE_CXXFLAGS*=$CXXFLAGS" "QMAKE_CXXFLAGS+=$MAC_ARCH_CXXFLAGS" 
"$SRCDIR/$TEST/$EXE.pro" -o "$OUTDIR/$TEST/Makefile"
  if [ "$VERBOSE" = "yes" ]; then
      OUTDIR=$OUTDIR "$@" && $MAKE && SUCCESS=yes
  else


Regards
Will


-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7471 9224
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7471 9224
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2015-09-15  8:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 10:06 [Buildroot] [PATCH 1/2] qt/qt5base: force gstreamer on configure Julien Corjon
2015-08-06 10:06 ` [Buildroot] [PATCH 2/2] qt/qt5multimedia: install gsttools for gstreamer1 Julien Corjon
2015-08-06 11:30 ` [Buildroot] [PATCH 1/2] qt/qt5base: force gstreamer on configure Baruch Siach
2015-08-08 13:16 ` Thomas Petazzoni
2015-09-15  8:37   ` Will Wagner [this message]
2015-09-15 10:35     ` Julien CORJON
2016-01-10 16:19 ` Yann E. MORIN
2016-01-12 11:50   ` Julien CORJON
2016-01-12 12:24     ` Peter Korsgaard
2016-01-19 20:31 ` Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2015-08-06 11:35 Julien CORJON

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=55F7D8BB.9040301@carallon.com \
    --to=will_wagner@carallon.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