Thanks for your work releasing nightlies.
I have just installed 9854 on Windows 7 and I am experiencing a problem that was not there before (i.e. I was using 9660)
My projects all have 4 build targets, 2 MSVC targets for use on Windows and 2 GCC targets for use on Linux. Some of these projects use wxWidgets, and therefore also wx-config. But wx-config on windows (wx-config-win) is really a different animal than wx-config on linux, using rather different options.
On both Windows and Linux I have defined a 'wx' global variable, and using it
Windows
<Compiler>
<Add option="/MD" />
<Add option="/GF" />
<Add option="/Ox" />
<Add option="/W3" />
<Add option="/EHsc" />
<Add option="`$(CPDE_USR)\bin\wx-config.exe --prefix=$(#wx) --wxcfg=$(#wx.release) --cxxflags`" />
<Add option="/D_CRT_SECURE_NO_WARNINGS" />
<Add option="/D_CRT_NONSTDC_NO_DEPRECATE" />
<Add option="/D_CRT_SECURE_DEPRECATE" />
</Compiler>
Linux
<Compiler>
<Add option="-std=c++0x" />
<Add option="-W" />
<Add option="-fPIC" />
<Add option="-DNOPCH" />
<Add option="-fexceptions" />
<Add option="-D_DEBUG" />
<Add option="-g" />
<Add option="`$(#wx.config) --cxxflags --debug`" />
</Compiler>
As you can see, there are different user defined fields for global variable 'wx' depending on which compiler is being used. The ".config" field is not used under Windows/MSVC for example.
However, when I now start CB 9854 with a MSVC compiler as default and open a C::B project, I now get "yellow boxes" popping up, complaining about missing global variable member definitions that are never going to be needed on this platform. This was never an issue before.