| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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-03-08 06:34:47 |
| Message-ID: | 20220308063447.GS27651@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 07, 2022 at 11:10:54AM -0800, Andres Freund wrote:
> On 2022-03-06 10:16:54 -0600, Justin Pryzby wrote:
> > On Fri, Mar 04, 2022 at 05:30:03PM -0800, Andres Freund wrote:
> > > I tried to use it, but saw that no caching was happening, and debugged
> > > it. Which yielded that it can't be used due to the way output files are
> > > specified (and due to multiple files, but that can be prevented with an
> > > msbuild parameter).
> >
> > Could you give a hint about to the msbuild param to avoid processing multiple
> > files with cl.exe? I'm not able to find it...
>
> /p:UseMultiToolTask=true
Wow - thanks ;)
> > I don't know about the issue with output filenames ..
>
> I don't remember the precise details anymore, but it boils down to ccache
> requiring the output filename to be specified, but we only specify the output
> directory. Or very similar.
There's already a problem report and PR for this.
I didn't test it, but I hope it'll be fixed in their next minor release.
https://github.com/ccache/ccache/issues/1018
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2022-03-08 06:46:37 | Re: Handle infinite recursion in logical replication setup |
| Previous Message | Masahiko Sawada | 2022-03-08 06:04:22 | Re: Add index scan progress to pg_stat_progress_vacuum |