Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-02 Thread Richard Purdie
On Wed, 2021-12-01 at 20:20 +, Mike Crowe via lists.openembedded.org wrote: > On Wednesday 01 December 2021 at 14:18:19 -0500, Justin Bronder wrote: > > On 01/12/21 16:43 +, Mike Crowe via lists.openembedded.org wrote: > > > I'm building for a specific chip and therefore don't wish to

Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-02 Thread Mike Crowe via lists.openembedded.org
Hi Alex, It's not a case of simply deleting the so files we don't need since the mesa build system stuffs everything into a small number of files and then hard links them together. For example, the current unmodified oe-core build for qemux86-64 yields: $ ls -l

Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-01 Thread Alexander Kanavin
I'd like to see specifics though to understand the use case better. What kind of target you're on, how much space will be saved by only building the driver you need and which driver is that? If the drivers are in separate .so objects, you can simply delete the ones you don't need from

Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-01 Thread Mike Crowe via lists.openembedded.org
On Wednesday 01 December 2021 at 14:18:19 -0500, Justin Bronder wrote: > On 01/12/21 16:43 +, Mike Crowe via lists.openembedded.org wrote: > > I'm building for a specific chip and therefore don't wish to waste time and > > electricity building and disk space on the target installing unwanted

Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-01 Thread Justin Bronder
On 01/12/21 16:43 +, Mike Crowe via lists.openembedded.org wrote: > I'm building for a specific chip and therefore don't wish to waste time and > electricity building and disk space on the target installing unwanted mesa > drivers. However, mesa.inc contains: > > GALLIUMDRIVERS = "swrast" >

Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-01 Thread Mike Crowe via lists.openembedded.org
Hi Alex, Thanks for responding. Just to make sure I understand, you think that I should add something like: PACKAGECONFIG[i915] = "" PACKAGECONFIG[iris] = "" PACKAGECONFIG[crocus] = "" GALLIUMDRIVERS:append = "${@bb.utils.contains('PACKAGECONFIG', 'i915', ',i915', '', d)}"

Re: [OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-01 Thread Alexander Kanavin
I think you do need to modify oe-core unfortunately, like is done for other drivers: PACKAGECONFIG[etnaviv] = "" GALLIUMDRIVERS:append ="${@bb.utils.contains('PACKAGECONFIG', 'etnaviv', ',etnaviv', '', d)}" Alex On Wed, 1 Dec 2021 at 17:44, Mike Crowe via lists.openembedded.org wrote: > I'm

[OE-core] Correct way to set DRIDRIVERS and GALLIUMDRIVERS from mesa bbappend

2021-12-01 Thread Mike Crowe via lists.openembedded.org
I'm building for a specific chip and therefore don't wish to waste time and electricity building and disk space on the target installing unwanted mesa drivers. However, mesa.inc contains: GALLIUMDRIVERS = "swrast" GALLIUMDRIVERS:x86-x32 = "" GALLIUMDRIVERS:append:x86:class-target =