On Thu, 17 Jul 2025 at 16:43, Daniel P. Berrangé <berra...@redhat.com> wrote:
>
> On Thu, Jul 17, 2025 at 03:30:06PM +0200, Stefano Garzarella wrote:
> > On Wed, 16 Jul 2025 at 13:31, Daniel P. Berrangé <berra...@redhat.com>
> > wrote:
> > > We really need to get something into 'make check' that runs the
> > > generator and compares its output to 'meson-buildoptions.sh' as
> > > we have hit this problem over & over again.
> >
> > Do we already have something similar for other generated files to be
> > inspired by?
>
> Not that I'm aware of.
In particular, meson-buildoptions.sh is an oddball, because the
most common patterns we have are:
(1) the generated file is not committed to version control
(2) the generated file is committed, but doing an update
requires an explicit manual action by somebody (examples
include all the guest BIOS files, and the results of
the update-linux-header.sh script)
The reason we keep hitting issues with meson-buildoptions.sh
is that it is both committed to version control *and* we
have meson build runes that will regenerate it automatically
when the input files are changed, which I think is a rare
combination.
thanks
-- PMM
