Hi all, I wanted to push this out before I'm ooo for 2 weeks of conferencing. With this we should be able to start CI'ing the meson build (ofc right now still in parallel with the automake stuff, and also using the results from the automake build for the hw testing CI does). The following should get meson going, and can be done in a build that's already been used to build using automake: $ mkdir build $ meson Note that everything gets autodetected, so no options really. $ ninja -C build $ ninja -C build test This series contains a patch to align the generated test lists between the two build systems. Comparing them would be a great validation of the match between meson/automake builds: $ diff tests/test-list.txt build/tests/test-list.txt Cheers, Daniel Daniel Vetter (3): meson: Simple makefile integration meson: align test-list.txt generation with automake meson: share the configuration_data object man/meson.build | 8 +------- meson.build | 32 +++++++++++++++++--------------- meson.sh | 35 +++++++++++++++++++++++++++++++++++ tests/Makefile.am | 1 + tests/Makefile.sources | 2 -- tests/generate_testlist.sh | 9 +++++++-- tests/meson.build | 20 ++++++++++++++------ 7 files changed, 75 insertions(+), 32 deletions(-) create mode 100755 meson.sh -- 2.14.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
