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: Adding CI to our tree (ccache) |
Date: | 2022-02-20 20:47:31 |
Message-ID: | 20220220204731.jm6mlhtradll2zvl@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2022-02-20 13:36:55 -0600, Justin Pryzby wrote:
> Have you tried to use the yet-to-be-released ccache with MSVC ?
Yes, it doesn't work, because it requires cl.exe to be used in a specific way
(only a single input file, specific output file naming). Which would require a
decent amount of changes to src/tools/msvc. I think it's more realistic with
meson etc.
> Also, do you know about msbuild /outputResultsCache ?
I don't think it's really usable for what we need. But it's hard to tell.
> Did you ever try to use clcache (or others) ?
>
> When I tried, it refused to cache because of our debug settings
> (DebugInformationFormat) - which seem to be enabled even in release mode.
> I wonder if that'll be an issue for ccache, too. I think that line may need to
> be conditional on debug mode.
That's relatively easily solvable by using a different debug format IIRC (/Z7
or such).
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2022-02-20 20:55:09 | Re: killing perl2host |
Previous Message | Peter Geoghegan | 2022-02-20 20:27:25 | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |