[Mesa-dev] initial meson port

[Daniel Stone]

Hi,
Sorry for the top-post but the Gmail mobile app no longer believes in
inline quoting.

As for installing newer Meson, that's not strictly needed. As you say,
Meson deliberately doesn't have difficult or changing dependencies. It can
also be run straight from a checkout without mangling $PATH or $PYTHONPATH.
Just specify the full path to meson.py and everything will work from there.
I've been working with Meson like that for a year or so (old Debian
packages and a deep distrust of pip), and it's yet to break on me.

It would even be possible to automate this from an autogen-style script.
Having done the numbers for the Wayland conversion, doing this in-tree
still takes less space than generating all the piles of guff that autogen
creates in your tree.

Cheers,
Daniel

On Thu, 28 Sep 2017 at 6:25 pm, Dylan Baker <dylan at pnwbakers.com> wrote:

> Quoting Tapani Pälli (2017-09-27 23:34:26)
> >
> >
> > On 09/27/2017 08:57 PM, Rob Herring wrote:
> > > 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.
> >
> > One possible issue is that meson and its dependencies are not part of
> > the supported toolchain for Android, would be surprised if this does not
> > become a problem on some level. As example version of Meson on Ubuntu
> > LTS (which is the tested and supported distro for android building) is
> > 0.29.0 while on Fedora 0.42.0.
>
> That will be a problem, I very much doubt that mesa will build with meson
> 0.29,
> and there are features going it 0.43 that I would like to depend on. Meson
> only
> has 2 hard requirements, python 3.4+ and ninja 1.6+, so it may be possible
> to
> install an updated meson via pip, but I suspect android will run into
> similar
> issues to windows, specifically that it needs a way to pass dependency
> locations.
>
> I've been looking at the possibility of generating blueprint from meson,
> which
> could the be checked into a branch, but there are some interface mismatches
> between meson and soong/blueprint and they could prove somewhat difficult
> to
> solve (specifically around arch specific files).
>
> Dylan
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170928/71de0c10/attachment.html>