Re: ccache, MSVC, and meson

From: Andres Freund <andres(at)anarazel(dot)de>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: ccache, MSVC, and meson
Date: 2022-05-24 20:30:39
Message-ID: 20220524203039.xyqjggtytsyizsbl@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-05-24 14:52:02 -0500, Justin Pryzby wrote:
> > The spurious message should be fixed, of course. I suspect you dont need a
> > wrapper, you can just set CC='ccache cl.exe' or similar? Afaics it's not
> > meaningful to do 'CC=ccache.exe' alone, because then it'll interpret arguments
> > as ccache options, rather than compiler options.
>
> if meson didn't crash CC=ccache.exe might have worked, because I had set
> CCACHE_COMPILER.

Did you report the issue? Should be simple enough to fix.

I seriously doubt it's a good idea to use CCACHE_COMPILER - there's no way
meson (or autoconf or ..) can rely on the results of compiler tests that way,
since CCACHE_COMPILER can change at any time.

> As I recall, CC='ccache cl.exe' didn't work because it didn't attempt to do any
> argument splitting.

I tried it, and it works for me when building with ninja (compiling with
cl.exe). I assume you are using msbuild?

A cached build takes 21s on my VM, fwiw, vs 199s uncached.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-05-24 20:58:41 Re: allow building trusted languages without the untrusted versions
Previous Message Zhihong Yu 2022-05-24 20:17:58 Re: adding status for COPY progress report