[Mesa-stable] [PATCH 1/3] android: broadcom/genxml: fix collision with intel/genxml header-gen macro

[Dylan Baker]

Quoting Rob Herring (2018-09-06 07:16:07)
> On Mon, Sep 3, 2018 at 4:27 PM Eric Anholt <eric at anholt.net> wrote:
> >
> > Mauro Rossi <issor.oruam at gmail.com> writes:
> >
> > > Fixes the following building error, happening when building both intel and broadcom:
> >
> > I wish someone maintaining android Mesa would work on making the meson
> > build work for them instead of just continuing to maintain the
> > Android.mk mess.
> 
> Trust me, no one likes this thankless job.
> 
> How do you envision that would work without meson support in the
> Android build system? I went down the path of defining a "prebuilt"
> Android.mk target which calls meson to do a build. This was a dead end
> because the Android.mk gets none of the build environment. It's
> possible to dump all that out and re-construct those settings. That
> seems horribly fragile, and I'd guess we'd just be switching from mesa
> to AOSP breaking the build. Of course the latter already happens too.
> Finally, I'm pretty sure this would not be accepted for the AOSP copy
> of mesa (which is trying to track mainline).
> 
> The other route would be some sort automatic meson to Android BP build
> file translation. Such a thing exists for autotools, but I've never
> seen it in actual use anywhere.
> 
> Either way, this seems like a unicorn to me until AOSP provides some
> support to support meson. If you really want to force the issue, strip
> all the Android.mk files out of mesa. Though that will mainly put the
> pain on downstream device trees, not AOSP.
> 
> Rob

With my meson hat on,

I've been looking at blueprint recently, trying to decide if we could implement
a meson-for-android on top of blueprint. While I know a lot about meson (I've
written a bunch of the meson implementation), I don't know a lot about blueprint
and their documentation is basically aimed at explaining how soong works. I
certainly can't commit to full time development on a meson-on-blueprint
implementation, but I certainly could help write one if there was someone
interested in working on it as well. It would also be helpful if there was
someone in the blueprint camp who could tell me whether such a thing is even
feasible or not.

Dylan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/mesa-stable/attachments/20180906/a3b2d0d8/attachment.sig>