Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <>
Subject: Re: [PR PATCH] [Merged]: [RFC] create build_helper for python3 cross-building
Date: Tue, 30 Aug 2022 05:25:07 +0200	[thread overview]
Message-ID: <20220830032507.rgB8wnhTX2tLLdJ2cv3xnmTe6Aj5Okd66uLk5oCNiSc@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

There's a merged pull request on the void-packages repository

[RFC] create build_helper for python3 cross-building

- common/build-helper/ add python3 helper
- common/{,environment}/build_style/ use python3 build_helper
- brltty: use python3 build_helper, clean up
- i2c-tools: use python3 build_helper
- libpwquality: use python3 build_helper
- tlsh: use python3 build_helper

My hope with this is to help with cross-building non-python packages that have python3 bindings/modules, but it can be used similar to the `rust` `build_helper` for various common constants, if needed.

One thing I'm not sure on is the usage with the `python3-module` `build_style`. It would cut down on the need to keep those env var definitions up-to-date in multiple places, but I'm open to opinions about it.

There's probably more packages that are marked `nocross`/`broken` because of python3 cross stuff that I didn't find.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**
    - packages changed seem to build the same thing as before, but weren't extensively tested

      parent reply	other threads:[~2022-08-30  3:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 19:30 [PR PATCH] " classabbyamp
2022-08-25 19:46 ` [PR REVIEW] " ahesford
2022-08-25 20:14 ` [PR PATCH] [Updated] " classabbyamp
2022-08-25 20:52 ` classabbyamp
2022-08-26  5:37 ` classabbyamp
2022-08-26  7:50 ` [PR REVIEW] " classabbyamp
2022-08-29  5:32 ` classabbyamp
2022-08-29 11:10 ` ahesford
2022-08-30  3:25 ` classabbyamp [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220830032507.rgB8wnhTX2tLLdJ2cv3xnmTe6Aj5Okd66uLk5oCNiSc@z \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).