From: Tim Orling <ticotimo@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-python][PATCH 0/2] Move "mesonpy" support to oe-core
Date: Mon, 19 Feb 2024 09:39:02 -0800 [thread overview]
Message-ID: <cover.1708364156.git.tim.orling@konsulko.com> (raw)
The "mesonpy" PEP-517 build backend is declared by python3-numpy in pyproject.toml,
so it is time to move this to oe-core.
This should not be build-tested/merged until the move to oe-core is complete:
https://patchwork.yoctoproject.org/project/oe-core/patch/cover.1708363628.git.tim.orling@konsulko.com/
This is part of a larger effort to replace usage of setuptools3.bbclass in favor of the
various python_*.bbclass PEP-517 build backends.
The following changes since commit a6c4624a684f7d5a2dbd21acbe74ecf611f4f839:
ot-br-posix: Limit vla-cxx-extension option to clang >= 18 (2024-02-10 23:47:57 -0800)
are available in the Git repository at:
https://git.openembedded.org/meta-openembedded-contrib timo/move_python_mesonpy
https://git.openembedded.org/meta-openembedded-contrib/log/?h=timo/move_python_mesonpy
Tim Orling (2):
python_mesonpy.bbclass: move to oe-core
python3-meson-python: move to oe-core
meta-python/classes/python_mesonpy.bbclass | 52 -------------------
.../python/python3-meson-python_0.15.0.bb | 23 --------
2 files changed, 75 deletions(-)
delete mode 100644 meta-python/classes/python_mesonpy.bbclass
delete mode 100644 meta-python/recipes-devtools/python/python3-meson-python_0.15.0.bb
--
2.34.1
next reply other threads:[~2024-02-19 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 17:39 Tim Orling [this message]
2024-02-19 17:39 ` [meta-python][PATCH 1/2] python_mesonpy.bbclass: move to oe-core Tim Orling
2024-02-19 17:39 ` [meta-python][PATCH 2/2] python3-meson-python: " Tim Orling
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=cover.1708364156.git.tim.orling@konsulko.com \
--to=ticotimo@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.