Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12121] New: PyQt5.QtSerialPort and other modules not being built.
Date: Sun, 18 Aug 2019 19:45:44 +0000	[thread overview]
Message-ID: <bug-12121-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12121
           Summary: PyQt5.QtSerialPort and other modules not being built.
           Product: buildroot
           Version: 2019.05.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: sahajsarup at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

when enabling python-pyqt5, many modules like PyQt5.QtSerialPort don't get
built because python-pt5 only has qt5base as dependencies.

So even if qt5serialport is enabled, the python module gets built first and
fails to find qtserialport installed, as reported by this error:

Project ERROR: Unknown module(s) in QT: serialport

Test:

A) Setup a regular buildroot build with python-qt5 and qt5 and qt5serialport
enabled. The error pops up.

B) Make clean. Run make qtserialport and then build python-qt5, and now the
serialport modules get built.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-08-18 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 19:45 bugzilla at busybox.net [this message]
2019-12-20 11:54 ` [Buildroot] [Bug 12121] PyQt5.QtSerialPort and other modules not being built bugzilla at busybox.net
2019-12-26 20:05 ` bugzilla at busybox.net

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-12121-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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