I would personally rather have scons and autotools than cmake. I've had the misfortune of using all three, and cmake is not an improvement in my opinion. Quoting Grazvydas Ignotas (2017-03-21 08:13:31) > It might make sense to give more attention to cmake just because many > mesa-related projects are already using it: llvm, piglit, vulkan > loader and demos, mesa-demos, etc. Not sure how well it supports BSDs > and windows, but everyone building graphics stacks or contributing to > mesa should already be comfortable with cmake thanks to piglit and > llvm, which might not be the case for meson. > > Gražvydas > > On Tue, Mar 21, 2017 at 4:44 PM, Jani Nikula > <jani.nikula@xxxxxxxxxxxxxxx> wrote: > > On Thu, 16 Mar 2017, Dylan Baker <dylan@xxxxxxxxxxxxx> wrote: > >> First it's written in python, [...] > > > > How does meson handle python 2 vs. 3? How do you avoid issues in the > > build files wrt this? On Debian meson seems to depend on python 3, so > > are they fully python 3? > > > > How does meson handle build file backwards compatibility between meson > > versions? I don't intend to flame, but I've found for some reason many > > python projects don't seem to take this very seriously. Either having > > conditionals in build files to support building with several meson > > versions or always requiring the latest and greatest version would be > > rather annoying. > > > > > > BR, > > Jani. > > > > -- > > Jani Nikula, Intel Open Source Technology Center > > _______________________________________________ > > dri-devel mailing list > > dri-devel@xxxxxxxxxxxxxxxxxxxxx > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
Attachment:
signature.asc
Description: signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
