I just have an idea that the problem is due to the fact that in the bad version has debug as only 圆4 and release as only 32-bit, and this mismatch is somehow corrupting the vcxproj xml. I don't know enough about how jucer creates vcxproj to know whether jucer is potentially messing up the vcxproj xml. Without going into crazy detail the problem has something to do with how the configurations are specified in the vcxproj xml. Notice how the bad version specifies 圆4 and 32-bit. jucer project is corrupt.įrom winmerge comparing old and new. jucer project from scratch and it works! Looks like the original.
jucer project is corrupt leading to a bad vs project?" I just tried creating a. But then I said, "well wait a minute, what if the. If I spent many hours learning exactly how the Visual Studio expects the vcxproj xml to be formatted maybe I could probably figure out exactly what introjucer is doing wrong. I did some more messing with WinMerge, I was able to get the properties page working in 2 out of 4 configurations (release 圆4 and debug win32).
0 kommentar(er)
