User forums > General (but related to Code::Blocks)

[Work In Progress] Patches to Compile C::B against wxWidgets 2.9.0

<< < (3/9) > >>

Biplab:

--- Quote from: stahta01 on May 03, 2009, 07:54:19 am ---FYI: The wx_str() is the same as c_str() under wxWidgets 2.8 and 2.6.

--- End quote ---

But the docs say otherwise. As per the docs, wx_str() is not defined for wx-2.8.x series. Yes, the return value is of same type.

stahta01:

--- Quote from: Biplab on May 03, 2009, 08:27:19 am ---
--- Quote from: stahta01 on May 03, 2009, 07:54:19 am ---FYI: The wx_str() is the same as c_str() under wxWidgets 2.8 and 2.6.

--- End quote ---

But the docs say otherwise. As per the docs, wx_str() is not defined for wx-2.8.x series. Yes, the return value is of same type.

--- End quote ---

The header file has it in it. It was depreciated, I am guessing, when the 2.0 series was released.

I can add guards but they are not really needed.

Tim S

stahta01:
@Biplab:

Possible method to add wx_str().

Does the following method meet with your OK?


--- Code: ---Deleted to save space

--- End code ---

TDragon:

--- Quote from: stahta01 on May 03, 2009, 06:30:54 am ---At one time, under windows GCC 4.x the wxWidgets would have runtime crashes if
CXXFLAGS="-fno-strict-aliasing" was not done. It might be fixed in wxWidgets or MinGW GCC 4.x.

--- End quote ---
FYI, this was only true for the 4.2 series; it has been fixed as of the 4.3 series.

Biplab:

--- Quote from: stahta01 on May 03, 2009, 10:59:49 am ---@Biplab:

Possible method to add wx_str().

Does the following method meet with your OK?

--- End quote ---

I'd prefer to have relevant code guarded with wxCHECK_VERSION. I'd prefer not to use prep.h for this.

FYI, I've patched most of the Core and Core Plugin code to ensure that build works fine. There are still many areas where I've missed out (as compiler didn't emit any warning).

Navigation

[0] Message Index

[#] Next page

[*] Previous page