Hi,
On 2025-06-30 19:42:51 -0400, Andres Freund wrote:
> On 2025-07-01 00:52:49 +0200, Daniel Gustafsson wrote:
> > > On 30 Jun 2025, at 20:33, Jacob Champion <jacob.champion@enterprisedb.com> wrote:
> > >
> > > On Mon, Jun 30, 2025 at 10:02 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> > >>> On 30 Jun 2025, at 18:58, Andres Freund <andres@anarazel.de> wrote:
> > >>> Probably just needs to be added to the installed_targets list.
> > >>
> > >> Thanks for the report, I'll take a look today to get it fixed.
> > >
> > > Thanks both!
> > >
> > > Looking at the installed_targets stuff, though... why do we use `meson
> > > install --no-rebuild` in combination with `depends:
> > > installed_targets`? Can't we just use Meson's dependency tracking
> > > during installation, and avoid this hazard?
>
> I don't think that's really possible - the dependency tracking is useful to
> generate granular *rebuild* information, but doesn't help with the first
> build.
>
> If we had dependency generation for the install target it could be helpful to
> discover missing dependencies though.
>
>
> > I suspect it is because without --no-rebuild the quiet target isn't entirely
> > quiet.
>
> No - the issue is that you're not allowed to run ninja while ninja is running,
> as that would corrupt it's tracking (and build things multiple times). meson
> install --no-rebuild would run ninja to build things...
>
>
> > Still, I was unable to make something that work in all build combinations
> > while keeping --no-rebuild (which isn't indicative of it being possible to
> > do).
>
> Hm, what problem did you encounter? I don't think there should be any
> difficulty?
Ping?
Greetings,
Andres Freund
