On Thu, Apr 10, 2014 at 04:59:25AM -0700, Vincent Cheng wrote:
> My understanding is that upstream is working towards porting
> codeblocks for wx 3.0, but it's currently not fully stable yet (e.g.
> #736368).
The issue there is most likely because wx 3.0 enables "WXDEBUG" mode
by default which includes checks for incorrect API usage, whereas with
wx 2.8 you had to specify it explicitly when you built the library. In
other words, codeblocks is misusing the wx API, but with 2.8 this gets
quietly ignored by default, whereas 3.0 reports it by default.
I bet if you rebuilt codeblocks using the WXDEBUG build of 2.8
(available in Debian in package libwxgtk2.8-dbg - despite the name, this
isn't debug symbols, but a separate build of the library) you'd see this
assertion too.
The simplest way to address this is to build codeblocks with -DNDEBUG
(pass it in CPPFLAGS usually), which makes wx 3.0 behave as a default
build of 2.8 would.
Cheers,
Olly
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
