All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-python][PATCH v2 1/4] python_mesonpy.bbclass: New class
Date: Thu, 23 Mar 2023 12:18:13 +0100	[thread overview]
Message-ID: <eee42b19-4c3a-e252-5590-42cc1506ea97@gmail.com> (raw)
In-Reply-To: <174EAFE93556A78F.19937@lists.openembedded.org>

2023. 03. 22. 9:18 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta:
> 2023. 03. 20. 17:26 keltezéssel, Ross Burton írta:
>> On 20 Mar 2023, at 15:01, Böszörményi Zoltán <zboszor@gmail.com> wrote:
>>> 2023. 03. 20. 15:46 keltezéssel, Ross Burton írta:
>>>> On 17 Mar 2023, at 07:25, Zoltan Boszormenyi via lists.openembedded.org 
>>>> <zboszor=gmail.com@lists.openembedded.org> wrote:
>>>>> +inherit setuptools3-base python3targetconfig python_pep517 meson-common
>>>> I still don’t see why you need to split the meson class up.
>>> See the other thread. For some reason, meson always wins
>>> regardless of the inheritance order, so do_configure has
>>> meson_do_configure instead of pep517_do_configure, etc.
>> Add a new do_configure to your class which simply calls the right one.
>
> It still doesn't work. meson_do_qa_configure fails with this: [...]

This construct also doesn't work
===================================
inherit meson
do_configure[postfuncs]:remove = "meson_do_qa_configure"
===================================

It results in an "unparsed line" error. So, I have to re-iterate this:

> Sorry, there seems to be no way around it but splitting out the
> environment setup from meson.bbclass into meson-common class.
> If you don't like the "-common" naming, I can rename it to
> meson-env.bbclass or something like that.
>
> I will still rework python3-meson-python to not require
> the dummy patchelf python module and review other
> comments and make necessary changes.



      parent reply	other threads:[~2023-03-23 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  7:25 [meta-python][PATCH v2 1/4] python_mesonpy.bbclass: New class Zoltán Böszörményi
2023-03-17  7:25 ` [meta-python][PATCH v2 2/4] python3-patchelf: New recipe Zoltán Böszörményi
2023-03-20 16:09   ` [oe] " Ross Burton
2023-03-17  7:25 ` [meta-python][PATCH v2 3/4] python3-pyproject-metadata: " Zoltán Böszörményi
2023-03-20 14:45   ` [oe] " Ross Burton
2023-03-17  7:25 ` [meta-python][PATCH v2 4/4] python3-meson-python: " Zoltán Böszörményi
2023-03-20 14:52   ` [oe] " Ross Burton
2023-03-20 14:46 ` [oe] [meta-python][PATCH v2 1/4] python_mesonpy.bbclass: New class Ross Burton
2023-03-20 15:01   ` Böszörményi Zoltán
2023-03-20 16:26     ` Ross Burton
2023-03-22  8:18       ` Böszörményi Zoltán
     [not found]       ` <174EAFE93556A78F.19937@lists.openembedded.org>
2023-03-23 11:18         ` Böszörményi Zoltán [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=eee42b19-4c3a-e252-5590-42cc1506ea97@gmail.com \
    --to=zboszor@gmail.com \
    --cc=Ross.Burton@arm.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.