Re: ccache, MSVC, and meson

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: ccache, MSVC, and meson
Дата
Msg-id 20220524203039.xyqjggtytsyizsbl@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: ccache, MSVC, and meson  (Justin Pryzby <pryzby@telsasoft.com>)
Ответы Re: ccache, MSVC, and meson  (Justin Pryzby <pryzby@telsasoft.com>)
Re: ccache, MSVC, and meson  (Justin Pryzby <pryzby@telsasoft.com>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Zhihong Yu
Дата:
Сообщение: Re: adding status for COPY progress report
Следующее
От: Nathan Bossart
Дата:
Сообщение: Re: allow building trusted languages without the untrusted versions