@Justin-Randall, in your update to #6 you mention the tradeoffs for relative path support and asked if "everyone [would] be OK with undefined debug behavior if the strange outcomes were well documented?". I imagine this would be acceptable to me, but also without relative path support almost all of the advantage of stashed would be lost for me. Could you go into what the kinds of strange outcomes might be? i.e. what the documentation might say.
Where possible, with the new feature, we will try to use relative paths. 3rd party libraries, system headers, etc... may be installed elsewhere, even if the content hash is identical. Currently Stashed chooses to treat that as a different hash (cache miss). If it did not, and your build retrieved some cache output built with different source locations, you may end up "missing" source files when debugging (as in, someone installed DirectX headers on their "F" drive, whereas you have them in a standard install location). The Visual Studio IDE will let you work around this manually, but it is probably not what most people would expect after building their changes and running under the debugger.
We really want Stashed to "just work" without much fuss, and where it would lead to different behavior, it should fall back to the compiler because "correct" is more important than "fast but incorrect".
In the case that the source is the same and only difference was its absolute location used for finding the source when debugging then I wouldn't consider the result to be incorrect. It isn't uncommon with prebuilt thrid party libraries to need to locate the source when debugging because it was located elsewhere on their build server. In my use case the system compiler and std library are in common locations and the application code and 3rd party libraries are located in slightly different directories both between users cmputers and betweent each of the copies of the repo on my own computer. So with relative path and content matching I would not only be able to get cache hits from other computers but also get more cache hits on my own computer.
Are the debug symbols for stashed.io releases available for download or on a symbol server somewhere?
The new debug generation flag Zf (used together with Zi,ZI), would that help to make stashed work with pdb files (Zi) also?
https://docs.microsoft.com/en-us/cpp/build/reference/zf?view=vs-2017
https://docs.microsoft.com/en-us/cpp/build/reference/zf?view=vs-2017
Another question, does anyone know if Z7 (C7) debug info is supposed to work with debugging coroutines?
hm, when using /Zi + pch, is it only for generating pch (/Yc + /Zi) stached will skip? using pch (/Yu + /Zi) workks with stashed?
is that a known problem?
after uninstalling it seems that a wrapper is still active since it is spamming this message when building:
"warning : Stashed service is not available. This will not be accelerated. Is the service running?"
"warning : Stashed service is not available. This will not be accelerated. Is the service running?"
In Logs, I get this Error: 2019/02/17 13:23:51.054 ERROR
Disable(): Object {reason: "msvs:v2017:211b1ebd:14.16.27023:x86_x64:remove d:\programs\microsoft visual studio\2017\community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x64\cl.exe: Access is denied."}
reason: "msvs:v2017:211b1ebd:14.16.27023:x86_x64:remove d:\programs\microsoft visual studio\2017\community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x64\cl.exe: Access is denied."
I want to demonstrate the advantages of this solution + incredibuild comparing times with or without stashed.io. What I'm doing is rebuild the project and taking times.
But I don't know how to enable/disable
Can someone help me figure that out ?
BTW I had the whole thing installed before any mention of licencing was encountered. I had thought it was free. Still, if it works well enough I can ask my company to pay and hope for the best!
I think they still let you pay for it though :/
I uninstalled it and am looking into just using ccache instead.
@janwilmans a lot of commits have been merged to ccache lately to support Windows and MSVC. Someone also releases binaries on github. I've not managed to get it to work yet mind you. stashed.io was cool though, except for the bug I hit which ended up costing more than the hours it saved me up til then!
