Re: meson uses stale pg_config_paths.h left over from make

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: meson uses stale pg_config_paths.h left over from make
Date: 2023-08-24 06:18:14
Message-ID: 1b46f0e3-f7c5-6451-20b5-4feca06a1120@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.08.23 14:52, David Rowley wrote:
> Generally when there are files left over the meson build script will
> detect this and ask you to run make maintainer-clean. That's useful
> on Linux, but on Windows you're just left to manually remove the
> conflicting files which are listed. Unfortunately, pg_config_paths.h
> wasn't listed, which I think was missed because it's not generated
> during configure, but during the actual make build. (see
> src/port/Makefile)

How is this different from any other built file being left in the tree?
Surely meson should not be required to detect that?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-08-24 06:25:47 Re: meson uses stale pg_config_paths.h left over from make
Previous Message Peter Eisentraut 2023-08-24 06:14:44 logical_replication_mode