Michael Biebl: > Am 24.03.2017 um 06:53 schrieb Michael Biebl: >> Am 24.03.2017 um 06:28 schrieb Niels Thykier: >>> Michael Biebl: >>> Wed, 12 Aug 2015 16:31:41 +0200 Niels Thykier <ni...@thykier.net> wrote: > >>>>> * Is it possible to reliably auto-detect if an upstream is using Meson >>>>> like it is with other build systems such as autoconf+make? >>>>> - If not, it can at best be a "manually invoked" build system. >>>> >>>> A meson.build file is probably a good indicator that meson is supported. >>>> As mentioned earlier, at least some of the GNOME projects will support >>>> autotools and meson/ninja in parallel for some time. So we'd need a >>>> mechanism to choose which one to use. >>>> >>> >>> There is an ordering inside debhelper to deal with that, which can be >>> changed during a compat bump. Possibly, we need some logic to keep the >>> meason build lower than the third-party build systems until then as well >>> (in the off-hand case that meason was /also/ available in packages with >>> those third party build systems - doubt it, but mentioning it for >>> completion). >> >> Thanks for the hint. I was already pointed at this on IRC. >> The biebl/meson branch adds meson to the list as last option. Which >> means a package shipping both autotools and meson support would get >> autotools by default, which is ok I guess. > > Related to that: For a source tree which ships both meson.build files > and configure.ac, autoreconf is run, even if I explicitly choose meson > via dh $@ --buildsystem=meson > > Niels, is there a way how I can skip the dh-autoreconf step(s) if meson > is used? > > Michael >
That would be #842246. The easiest thing is probably just overriding command. ~Niels
