From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Markus Volk" <f_l_k@t-online.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 1/2] llvm: make LLVM_HAVE_OPT_VIEWER_MODULES optional
Date: Thu, 23 Jun 2022 10:41:15 +0200 [thread overview]
Message-ID: <20220623104115.11e5264a@booty> (raw)
In-Reply-To: <291f23ad-b932-e3ed-ca7a-f0f29fd576ba@t-online.de>
Hi Markus,
On Thu, 23 Jun 2022 09:57:11 +0200
"Markus Volk" <f_l_k@t-online.de> wrote:
> Hi Luca,
>
> the reason i made the switch working manually both sides was that i
> wanted to remove those python modules from build dependencies as i
> thought they would only be needed at runtime.
Sure, fair enough.
As for me, I preferred to do the opposite because the CMake
configuration process might look into anything specific of those
modules, and if they add such code in future versions we might not
notice and experience issues. Maybe unlikely, but my approach was to
prefer a "safe" build to build time.
It's a matter of choice I guess, no approach is clearly "wrong" or
"right" here.
> But this should work as
> well and I'm of course OK with it.
OK. My v2 is under testing right now.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-06-23 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 17:32 [oe-core][PATCH 1/2] llvm: make LLVM_HAVE_OPT_VIEWER_MODULES optional Markus Volk
2022-06-22 17:32 ` [oe-core][PATCH 2/2] llvm: dont use host python Markus Volk
2022-06-22 20:44 ` [oe-core][PATCH 1/2] llvm: make LLVM_HAVE_OPT_VIEWER_MODULES optional Luca Ceresoli
2022-06-22 21:03 ` Markus Volk
2022-06-23 7:40 ` Luca Ceresoli
2022-06-23 7:57 ` Markus Volk
2022-06-23 8:41 ` Luca Ceresoli [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=20220623104115.11e5264a@booty \
--to=luca.ceresoli@bootlin.com \
--cc=f_l_k@t-online.de \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox