[debhelper-devel] Bug#795253: Bug#795253: Bug#795253: Add support for Meson build system

Niels Thykier niels at thykier.net
Wed Mar 29 06:14:00 UTC 2017


Michael Biebl:
> Am 25.03.2017 um 08:58 schrieb Niels Thykier:
>> Michael Biebl:
>>> Am 24.03.2017 um 06:53 schrieb Michael Biebl:
> 
>>> 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.
> 
> Hm, I see, so apparently/obviously other build systems are affected by
> this as well.
> 
> By overriding, do you mean, that package maintainers have to that
> manually via
> 
> %:
> 	dh --without autoreconf
> 
> Or did you mean something else?
> 

That or an empty "override_dh_autoreconf" target.

> Ideally dh_update_autotools_config and dh_autoreconf are only run if the
> active build system is autotools.

True, though I suspect that most packages will just have a slightly
expense "noop" (or "noise-op").  I am aware of I think 1 package where
it is an actual problem (the package listed in #842246) because
autoreconf actually fails.

> Is it possible to change dh to only add the autoreconf sequence
> depending on whether autotools is the active build system (not just
> autodetected).
> 

Patches are welcome.

I think it is "just" a question of having a "reconfigure" step, which
would have this logic and only do those changes if it is an autotools
based build.

FYI: The primary thing keeping me back from merging dh-autoreconf fully
is the optional patching to "libtool".  If we can have that merged into
libtool itself, I am happy to completely integrate dh-autoreconf.

> Or is it possible to decide this from within the
> dh_update_autotools_config and dh_autoreconf helpers so they are always
> run but become a nop if buildsystem != autotools ?
> 
> 

In theory, yes, but AFAIR the auto-detection logic/build system
selection logic is currently not available outside a "build tool".  It
would probably have to be separated.

If it was, dh could also grow an "--list-buildsystems" so you don't have
to use "dh_auto_build --list" for that.

Thanks,
~Niels




More information about the debhelper-devel mailing list