Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Dragon <hypnotoad@lindra.de>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] python-sip: fix compile error
Date: Tue, 12 Dec 2023 16:20:43 +0100	[thread overview]
Message-ID: <65def2db-75ce-4eb0-88ac-28eaf310d21d@lindra.de> (raw)
In-Reply-To: <36de4fd0-85f8-46a4-9146-05029704f458@lindra.de>

Dear all,

here is my conclusion regarding sip6:

The library discontinues the "sip" tool that configure.py of pyqt5 
searches. Instead, one should use PyQt-builder (which is easy to 
package) and the sip-build tool [1]. However, when I get it working I 
run into the same problem which once was fixed python-pyqt5.mk: 
sip-build actually does compile and executes a test binary called 
cfgtest_QtCore, similar to what a configure.sh script does. The output 
file cfgtest_QtCore.out is currently created by a buildroot hook in 
python-pyqt5.mk. With sip-build, another solution seems needed because 
sip-build deletes the file instead of skipping the execution of 
cfgtest_QtCore. It then tries to execute cfgtest_QtCore which is 
compiled for the target.

I am neither a buildroot nor a python expert and do not know the proper 
way to enforce that this is done with the host compiler and the rest of 
the compilation is done for the target. If that would be fixed, then one 
could probably easily also get pyqt6 to run. So it would be good if 
someone could have a look at this, but I cannot do that soon.

Best,

Ralf

[1] https://www.riverbankcomputing.com/static/Docs/PyQt5/installation.html#building-pyqt5




_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-12-12 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 17:41 [Buildroot] [PATCH 1/1] python-sip: fix compile error Ralf Dragon
2023-11-25 22:04 ` Yann E. MORIN
2023-11-27 21:14   ` Ralf Dragon
2023-11-29  6:42     ` Yann E. MORIN
2023-11-29 22:10       ` Ralf Dragon
2023-12-12 15:20         ` Ralf Dragon [this message]

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=65def2db-75ce-4eb0-88ac-28eaf310d21d@lindra.de \
    --to=hypnotoad@lindra.de \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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