Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Build C::B against wx3.02 with gcc 5.2 under Windows

<< < (8/25) > >>

ollydbg:
One thing I forgot to mention is that switch between wx3.0.2 debug or release library is quite simple, you just need to change the link library name.


--- Code: --- src/CodeBlocks_wx30.cbp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/CodeBlocks_wx30.cbp b/src/CodeBlocks_wx30.cbp
index 61c6659..7b04c37 100644
--- a/src/CodeBlocks_wx30.cbp
+++ b/src/CodeBlocks_wx30.cbp
@@ -700,7 +700,7 @@
  </Target>
  <Environment>
  <Variable name="WX_CFG" value="" />
- <Variable name="WX_SUFFIX" value="u" />
+ <Variable name="WX_SUFFIX" value="ud" />
  <Variable name="WX_VERSION" value="30" />
  </Environment>
--- End code ---

No need to add the "__WXDEBUG__" for the debug version, since both debug and release version of wxWidgets library have "__WXDEBUG__" defined.

ollydbg:

--- Quote from: ollydbg on September 27, 2015, 09:18:08 am ---After finishing building CodeBlocks_wx30.cbp and running update30.bat, I just start C::B inside C::B.
The first thing I see is a dialog from wx, says

--- Quote ---15:23:36: Resource files must have same version number.
15:23:38: Resource files must have same version number.

--- End quote ---
I think I have reported some where in this forum, but it is lost...

--- End quote ---
It is here: warning message about resource version number incorrect, and the two warning above was caused by local patch files which does not belong to C::B trunk.  :)

MortenMacFly:

--- Quote from: ollydbg on September 29, 2015, 12:23:39 am ---Good catch, so it should be "if(sFnt.Len() == 0)", right?

--- End quote ---
Yes.

MortenMacFly:

--- Quote from: ollydbg on October 04, 2015, 01:24:26 pm ---It is here: warning message about resource version number incorrect, and the two warning above was caused by local patch files which does not belong to C::B trunk.  :)

--- End quote ---
I've answered in the other thread.

scarphin:

--- Quote from: ollydbg on October 04, 2015, 10:09:25 am ---
--- Quote from: scarphin on September 28, 2015, 04:43:30 pm ---I use '-o3' for my x32 and x64 builds all the time and I don't have such a crash issue. My version for mingw-builds is 4.9.2 though. I used your method to overcome the pch issue to be able to compile 64-bit cb. Maybe you should try '-o3'.

--- End quote ---
Currently, I would still suggest using -O0 option to build both wxWidgets 3.0.2 and C::B trunk, at least it don't crash on my windows XP.
Do you have a 32 bit C::B (include the wx 3.0.2 library)which you build with '-o3' option? If you don't have a Windows XP system, You can upload some where, and PM the link, I'd like to test it, thanks.

--- End quote ---
Hmm, I think my comment caused a confusion, my apologies. I'm not using cb with wx3.0, I'm still using it with wx2.8. I just wanted to emphasize that using '-o3' doesn't make my build crash or behave abnormal in some way. It's just as stable as a normal nightly if not more. I also built wx2.8 with default release option, I think it is '-o2' and I didn't change it. Sorry for the confusion again. I'm very busy currently to make any wx3.0 build but I think I have a ready to use wx3.0 build so I may try building cb when and if I can find some time. Do you require an xp or a win7 build? I'll pm you a link if I success (again if I can find some time, no promises ;)). Lastly be aware I'm using mingw-builds compiler not tdm if that matters.

Navigation

[0] Message Index

[#] Next page

[*] Previous page