meson fails to link LLVM on my setup, so I can't use it, therefore all my
meson changes are untested.

Even if meson worked, I have to use make, because that's what users use.

This change simplifies the meson build too.


On Mon, Apr 9, 2018 at 2:21 PM, Dylan Baker <> wrote:

> Have you tried using the meson build if you're that concerned about build
> times?
> The plan remains to remove the autotools build at some point, so creating a
> massive amount of churn in the autotools build that may or may not break
> something to get some amount of speedup when you could just change tools
> and get
> a better speedup seems odd to me.
> (meson -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=radeonsi)
> for reference, with cold ccache:
> ninja -C build-si -j6  703.15s user 56.77s system 383% cpu 3:17.94 total
> and a hot:
> ninja -C build-si -j6  54.36s user 6.72s system 340% cpu 17.929 total
> compared to autotools
> (./configure --without-dri-drivers --without-vulkan-drivers
> --with-gallium-drivers=radeonsi)
> cold:
> make -j6  827.63s user 72.89s system 339% cpu 4:25.34 total
> hot:
> make -j6  175.09s user 24.42s system 278% cpu 1:11.64 total
> Just to be clear, meson/ninja doesn't suffer from the recursive make
> problem
> that autotools does. There is no way you can get the same level of
> performance
> from make without reducing the autotools build to gibberish.
> Dylan
mesa-dev mailing list

Reply via email to