From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: peter.marko@siemens.com,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
"alex@linutronix.de" <alex@linutronix.de>,
Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 3/6] mesa: enable a rich set of drivers for native builds
Date: Sat, 3 Aug 2024 07:13:53 +0200 [thread overview]
Message-ID: <90759604-7a95-4ef5-b03b-c66fb6107583@gmail.com> (raw)
In-Reply-To: <AS1PR10MB5697ED6BE1D46C5AEA0B2267FDB32@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
2024. 08. 02. 19:52 keltezéssel, Peter Marko via lists.openembedded.org írta:
>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-
>> core@lists.openembedded.org> On Behalf Of Alexander Kanavin via
>> lists.openembedded.org
>> Sent: Thursday, March 16, 2023 10:41
>> To: openembedded-core@lists.openembedded.org
>> Cc: Kanavin, Alexander (EXT) (Linutronix GmbH) <alex@linutronix.de>
>> Subject: [OE-core] [PATCH 3/6] mesa: enable a rich set of drivers for native
>> builds
>>
>> Without this, the only available driver would be swrast
>> (without llvmpipe) which is far too slow to be practical,
>> and so qemu wouldn't be able to perform accelerated graphics.
>>
>> The one major dependency pulled in by this change is llvm-native
>> which takes just under three minutes on my machine. If this is
>> undesitable, opengl can be removed from DISTRO_FEATURES_NATIVE.
> I was just hit by this commit when migrating our gui layers from kirkstone to scarthgap.
> We include clang-native in our sdk and this creates conflict:
> ERROR: product-image-sdk-1.0-r0 do_prepare_recipe_sysroot: The file /usr/bin/llvm-lto2 is installed by both llvm-native and clang-native, aborting
>
> I had to create mesa_%.bbappend which replaces llvm with clang
> PACKAGECONFIG[gallium-llvm] = "-Dllvm=enabled -Dshared-llvm=enabled, -Dllvm=disabled, clang clang-native elfutils"
>
> But bbappends are bad idea for config changes and should be only used as last resort so I'd like to solve it via distro config.
> Also update-alternatives doesn't work for native recipes I think.
>
> Any idea how to solve this in a nice way?
> One idea from me would be to create global LLVM_PROVIDER and LLVM_NATIVE_PROVIDER variables which could be automatically switched in meta-clang.
> Wdyt?
This is already documented in meta-clang.
Though it's not automatic, you have to add it manually to
your custom distro's configuration or local.conf.
https://github.com/kraj/meta-clang?tab=readme-ov-file#providing-llvm
next prev parent reply other threads:[~2024-08-03 5:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:40 [PATCH 1/6] runqemu: direct mesa to use its own drivers, rather than ones provided by host distro Alexander Kanavin
2023-03-16 9:40 ` [PATCH 2/6] mesa: allow mesa-native/nativesdk only subject to opengl/vulkan DISTRO_FEATURE Alexander Kanavin
2023-03-16 9:40 ` [PATCH 3/6] mesa: enable a rich set of drivers for native builds Alexander Kanavin
2023-03-20 17:10 ` [OE-core] " Ross Burton
2023-03-20 17:41 ` Alexander Kanavin
2024-08-02 17:52 ` Marko, Peter
2024-08-03 5:13 ` Böszörményi Zoltán [this message]
2023-03-16 9:41 ` [PATCH 4/6] llvm: allow building libllvm in native builds, subject to PACKAGECONFIG Alexander Kanavin
2023-03-20 16:20 ` [OE-core] " Ross Burton
2023-03-20 17:36 ` Alexander Kanavin
2023-03-16 9:41 ` [PATCH 5/6] mesa: do not strip rpaths from dri drivers Alexander Kanavin
2023-03-16 9:41 ` [PATCH 6/6] mesa: update 22.3.5 -> 23.0.0 Alexander Kanavin
2023-03-18 2:47 ` [OE-core] " Khem Raj
2023-03-18 8:01 ` Alexander Kanavin
2023-03-18 18:37 ` Khem Raj
2023-03-18 18:57 ` Martin Jansa
2023-03-20 7:09 ` Alexander Kanavin
2023-03-20 10:01 ` Richard Purdie
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=90759604-7a95-4ef5-b03b-c66fb6107583@gmail.com \
--to=zboszor@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=raj.khem@gmail.com \
/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