All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14606] New: Updated qt5webkit issue in 2022.02-rc2
Date: Thu, 24 Feb 2022 01:44:58 +0000	[thread overview]
Message-ID: <bug-14606-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14606

            Bug ID: 14606
           Summary: Updated qt5webkit issue in 2022.02-rc2
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: brock@cottonwoodcomputer.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Testing my build against 2022.02-rc2 and qmake fails to build our Qt project:
Project ERROR: Unknown module(s) in QT: webkit

Digging into it a bit, the updated qt5webkit package appears to be installing
the mkspecs into the target instead of the host.  Also the mkspecs have
hardcoded library and include paths instead of using $$QT_MODULE_INCLUDE_BASE
etc like the other Qt packages

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-02-24  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  1:44 bugzilla [this message]
2024-06-15 15:00 ` [Buildroot] [Bug 14606] Updated qt5webkit issue in 2022.02-rc2 bugzilla

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=bug-14606-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 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.