Hi Daniel,
Okay, makes sense that you don’t want to have to repeat the dependencies’
builds for every CI test. I’m not arguing that you should – it was just more a
thought experiment to see whether riding Meson subprojects is a reasonable idea
for establishing a development environment.
I get
Hi Matt,
On Fri, 7 Jun 2024 at 15:30, Hoosier, Matt wrote:
> Would Meson’s dependency wrapping capabilities be a viable solution here? I
> think that most of Weston’s dependencies that have aggressive version
> requirements are themselves also Meson projects.
>
> The Weston CI configuration bui
Would Meson’s dependency wrapping capabilities be a viable solution here? I
think that most of Weston’s dependencies that have aggressive version
requirements are themselves also Meson projects.
The Weston CI configuration builds a bunch of its dependencies (Mesa, libdrm,
libwayland …) manually
> What do you mean you can capture all virtual machines with KMS
writeback?
>
> What's the architecture there? How do virtual machines access KMS
hardware? Why would Weston be able to capture their outputs at all?
The world of virtualization on commercially supported embedded SOCs for
big-scale p
