Re: TempFileMunge conflicts with ccache

Andrew,

Just a thought. (without looking at the code yet).
Would being able to provide a scanner for the action to find the implicit
dependencies from the action be of value?
(Sounds like in this case it could, and maybe generally?)

-Bill

On Wed, Dec 19, 2018 at 10:15 AM Mats Wichmann <[email protected]> wrote:

> On 12/6/18 10:14 AM, Andrew C. Morrow wrote:
>
> > It appears that TempFileMunge just assumes that only the first token of
> the
> > command is actually the "compiler", and ends up feeding the response file
> > directly to ccache, rather than invoking, say `ccache
> > g++ @/path/to/temp/file`.
> >
> > On the other hand, could this even work in principle? Is ccache smart
> > enough to know to "see into" the response file in order to interact with
> > its cache correctly?
>
> ccache doesn't deal with complex lines at all (specifically including
> link lines), it just punts it to the compiler.  So in theory it "should
> work" - by not doing anything.  Whether that's true or not in practice...
>
> _______________________________________________
> Scons-users mailing list
> [email protected]
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users