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

Building Code::Blocks on Win 64

<< < (14/15) > >>

MortenMacFly:

--- Quote from: stahta01 on February 21, 2012, 02:43:01 pm ---There is about 100 #ifdef that are not needed in Code::Blocks because of the c_str/wx_str functions where in 2.8 wx_str is defined the same as c_str but I could not use it because it was not documented.

--- End quote ---
I agree on probably not using methods / classes that are back-ported from wx2.9.x and are either not documented or encapsulated in a special "#if wxABI_VERSION >= 208XX". But this specific function is there for ages and works. In addition it does exactly the same as the 5-liner "#ifdef" in Code::Blocks. Maybe I am missing something but honestly I don't see a reason not to use it. Did I told you so?


--- Quote from: wx/include/string.h ---
--- Code: ---    // identical to c_str(), for wxWin 1.6x compatibility
    const wxChar* wx_str()  const { return c_str(); }

--- End code ---

--- End quote ---

stahta01:

--- Quote from: MortenMacFly on February 21, 2012, 02:53:31 pm ---Did I told you so?

--- End quote ---

I do NOT think that you were the one who said no to it. But, one of the CB Dev team did.

I just added all the #if guards because I wanted to get the original 2.9 patch(s) applied.

I planned to submit a patch removing the #if 2.9 when wxWidgets 3.0 is released.

Tim S.

 

MortenMacFly:

--- Quote from: jens on February 20, 2012, 12:48:33 pm ---This should be fixed in actual trunk and will surely make it in Biplab's win64-build.
It also occurs on linux 64-bit with wx2.9 if debug-messages are on.

--- End quote ---
BTW: What drives me nuts are these warnings:

--- Code: ---../../src/common/menucmn.cpp(976): assert "item" failed in Enable(): attempt to enable an item which doesn't exist

--- End code ---
Did anyone already figured out a good way how to catch them? They occur in every call to updateui, so very often and the debugger gets crazy after a while...

Jenna:

--- Quote from: MortenMacFly on February 25, 2012, 09:51:04 am ---
--- Quote from: jens on February 20, 2012, 12:48:33 pm ---This should be fixed in actual trunk and will surely make it in Biplab's win64-build.
It also occurs on linux 64-bit with wx2.9 if debug-messages are on.

--- End quote ---
BTW: What drives me nuts are these warnings:

--- Code: ---../../src/common/menucmn.cpp(976): assert "item" failed in Enable(): attempt to enable an item which doesn't exist

--- End code ---
Did anyone already figured out a good way how to catch them? They occur in every call to updateui, so very often and the debugger gets crazy after a while...

--- End quote ---
I don't get them on linux.
I will try on win7, nbut I do not have a 64bit build of wx at the moment.
But I will see if I get them here also.

MortenMacFly:

--- Quote from: jens on February 25, 2012, 10:01:44 am ---I will try on win7, nbut I do not have a 64bit build of wx at the moment.

--- End quote ---
Its not 64 bit related, but wx2.9.x and they come from OnSearchMenuUpdateUI btw...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version