User forums > Nightly builds

The 02 August 2014 build (9854) is out.

<< < (2/4) > >>

cacb:
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.

oBFusCATed:

--- Quote from: cacb on August 05, 2014, 09:46:00 am ---This was never an issue before.

--- End quote ---
C::B is more vocal about invalid global variables now, so just put something to silence it and you're good to go.

cacb:

--- Quote from: oBFusCATed on August 05, 2014, 10:33:14 am ---C::B is more vocal about invalid global variables now, so just put something to silence it and you're good to go.

--- End quote ---

Ok, seems to work on Windows. Thanks.

ToApolytoXaos:

--- Quote from: ToApolytoXaos on August 03, 2014, 08:54:04 am ---The parser issue with header files still exists; if you create a new header file and try to include any header file, it won't suggest anything at all, neither header file names nor C++ keyword tags; only the current header's name.

--- End quote ---

I have just tested the same proceduce on Windows XP (VirtualBox) and it works just fine; the issue insists on GNU / Linux. By the way, on Windows it behaves so nice, so smoothly, and so freaking fast, let alone accurate results!

Well done, team!

oBFusCATed:
Are you doing the 100% exact steps to reproduce the problem? Can you post them?

Navigation

[0] Message Index

[#] Next page

[*] Previous page