With the attached screen shot, I'm pretty sure found out the issue and attached the way to fix the issue (i.e. delete the src\chrome\Debug directory).
Please note that the projects are configured in such a way that the output directory is always immediately below the .sln file placement. Hence opening a different .sln will use a different intermediary and output directories. Finally, note that the precompiled headers are only used in debug, not in release. Precompiled header assumes that the included headers in this file never change and thus requires a full rebuild when any of these change. M-A 2008/9/20 Hector <[EMAIL PROTECTED]>: > > People, I've been trying hard to figure out why the net project is > failing with winhttp.h and specstrings.h related stuff. I've been > racking my brains over this because yuns all said its all perfect. > Googling winhttp.h and specstrings.h shows this is not an uncommon > related to mixed compiler vs SDK setups. But discussions all seem to > indicate I should be ok even with older SDK. But why with 2008 > SDK? There shouldn't be a problem. > > So because the IDE was too slow loading the CHROME solution and even > recompiling, I began to load just the individual projects to that I > can atleast do some rapid tries and errors here. > > When I did this PUFF!! It COMPILED!!!! > > I submitted this as an issue: > > http://code.google.com/p/chromium/issues/detail?id=2576 > > mainly to get it documented with a screen shot. of two VS2005 IDE > windows, the left side has the net.sln project only, and the right > side has the entire chrome.sln loaded. > > Simply compiling the single source code proxy_resolver_winhttp.cc > (highlight file, right click compile), and you will see it compile > successful when the project is by itself, but fails when loaded with > the chrome solution. > > I beat my brains to see the different in the properties - none. I > went to command line for the net.sln and it succeeds, but doing the > same with the entire solution, it fails. > > Obviously, something is being inherited but that should not be the > case - the project should compile on its own as it does. But fails > when loaded with the entire solution? Weird! > > What on earth could this be? > > -- > HLS > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
