[Mesa-dev] initial meson port

[Rob Herring]

On Wed, Sep 27, 2017 at 12:38 PM, Eric Anholt <eric at anholt.net> wrote:
> Dylan Baker <dylan at pnwbakers.com> writes:
>
>> [ Unknown signature status ]
>> I've gone ahead and pushed the Vulkan drivers meson builds.
>>
>> For those interested in helping finish the conversion, I have a branch
>> "wip/meson-4" on my github (github.com/dcbaker/mesa) that has i965 and most of
>> the core classic mesa stack building. I'm working on GLX, then EGL to start
>> testing this stack. Getting gallium building is my next step after that (it'll
>> be RadeonSI because I have hardware).
>>
>> I'm also working on getting features into upstream meson to make meson more
>> comfortable for mesa. Currently there are patches landed or pending for the two
>> workarounds in the meson build we have currently (choosing the right linker and
>> indexing into CustomTargets). I'm also still thinking about how we can share
>> source files with the other 3 build systems already in mesa (autotools and
>> android being the most important, since hopefully our meson will be able to
>> support windows in the future, I don't know what will happen when android moves
>> to blueprint/soong). If there is anything else please let me know.
>
> Talking with ChromeOS folks at XDC, it sounded like having Android.mk be
> a small wrapper around another build system is a totally acceptable and
> not unusual thing to do.  Rob, does that seem possible/OK to you?  It
> seems like that should seriously reduce the android maintenance burden.

I haven't come across any examples doing that, but it seems fine to me
if that can work. I'd guess we just need to create a prebuilt target
and somehow trigger it to run meson. It could be problematic if
anything in mesa is a dependency on another project as there's some
expectations about where things are built. But I don't think mesa is a
dependency for anything.

Rob