Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-29 Thread Alexander Kanavin
On Thu, 29 Feb 2024 at 09:20, Philip Lorenz wrote: > > One possibility is teaching it to mass-import pre-computed entries > > into its index, so that sweeping file tree scans with archive > > extractions can be avoided altogether. Or doing incremental index > > imports directly from do_package. >

Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-29 Thread Philip Lorenz
Hi Alex, On 28.02.24 18:40, Alexander Kanavin wrote: On Wed, 28 Feb 2024 at 16:41, Philip Lorenz wrote: I'm assuming this data wouldn't be that large or that expensive to compute so I'd prefer not to hide it behind extra configuration options if we can help it. That does depend on the

Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-28 Thread Alexander Kanavin
On Wed, 28 Feb 2024 at 16:41, Philip Lorenz wrote: > > I'm assuming this data wouldn't be that large or that expensive to > > compute so I'd prefer not to hide it behind extra configuration options > > if we can help it. That does depend on the overheads/costs though. > > > I just executed build

Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-28 Thread Philip Lorenz
Hi Richard, On 28.02.24 10:14, Richard Purdie wrote: On Wed, 2024-02-28 at 07:21 +0100, Philip Lorenz wrote: With the introduction of debuginfod ([1]), providing debug symbols to developers has been greatly simplified. Initial support for spawning a debuginfod server is already available as

Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-28 Thread Philip Lorenz
Hi Alex, On 28.02.24 08:41, Alexander Kanavin wrote: On Wed, 28 Feb 2024 at 07:22, Philip Lorenz wrote: However, this relies on debuginfod scraping the debug packages for their build IDs. This is not only inefficient (as all packages need to be extracted again), but it also does not scale

Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-28 Thread Richard Purdie
On Wed, 2024-02-28 at 07:21 +0100, Philip Lorenz wrote: > With the introduction of debuginfod ([1]), providing debug symbols to > developers has been greatly simplified. Initial support for spawning a > debuginfod server is already available as part of poky. > > However, this relies on debuginfod

Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-27 Thread Alexander Kanavin
On Wed, 28 Feb 2024 at 07:22, Philip Lorenz wrote: > However, this relies on debuginfod scraping the debug packages for their > build IDs. This is not only inefficient (as all packages need to be > extracted again), but it also does not scale well when covering a large > number of builds. Is it

[OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files

2024-02-27 Thread Philip Lorenz
With the introduction of debuginfod ([1]), providing debug symbols to developers has been greatly simplified. Initial support for spawning a debuginfod server is already available as part of poky. However, this relies on debuginfod scraping the debug packages for their build IDs. This is not only