-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not compatible with PCH #20
Comments
PCH is a bit of an issue. Information about the compiled PCH is stored in the application PDB, but it can't be specified on the command-line or else the compiler will attempt to modify it, which won't work while the application is running. blink could copy it to a temporary location and specify that path to workaround this. But what then what happens if the user decides to modify the file generating the PCH? All future compiles would now reference the old PCH data from the application PDB, which no longer makes sense. |
Yeah quite tricky, you could also try to disable PCH but most code out there probably does not compile both ways. By the way what I tested was the Win32 (GUI) sample project VS generates. That uses PCH by default. |
@crosire It would be great if this limitation was advertised on the readme. Too bad it won't work, I was excited to try this out on my project! |
blink should still work, it will just take longer to compile a change, since it cannot make use of PCH data. |
It looks like it gets setup fine, but then once I make a code change (in this case to main.cpp) I get the following output:
I'm compiling with /ZI, are there any other flags which are necessary? (Edit and Continue for example?) |
See #32 (comment) |
because it removes /ZI? At least cl was called without any /Z* debug option
error C2855: commandline option '/Z7' inconsistent with precompiled header
The text was updated successfully, but these errors were encountered: