#17 Support for building codeblocks with wxwidgets 3.0?

[Vincent C.]

Is building codeblocks with wxwidgets 3.0 a supported configuration? The wiki and various forum threads like this one seem to suggest that this isn't the case (at least, with the current stable release). Is there a set of patches that I could perhaps cherrypick from svn for codeblocks to work with wx 3.0? Thanks!

(Forwarding from https://bugs.debian.org/744115 )

[ollydbg]

If I remember correctly, there are many discussions about building against wx3.0 in C::B forum. Building against wx3.0 is not quite that hard I think, but make the build stable like wx2.8 need a lot of testing.

[Vincent C.]

Building codeblocks against wx3.0 works fine with the current set of packages in Debian/Ubuntu; I'm more worried about runtime problems (e.g. https://bugs.debian.org/736368 ). Ideally I'd wait for a new codeblocks release before making this change in Debian, but since wx2.8 is due to be removed before the next Debian release, I was hoping that I could just pull a set of wx3.0-related commits from e.g. svn trunk, in the meantime.

[ollydbg]

Hi, Vincent, I will discuss this issue with other C::B devs. From my point of view, pulling a set of commits from the svn trunk to release 13.12 code base is hard, maybe a new release 14.xx is better. Thanks.

[Olly Betts]

Did anything come of those discussions?

As things currently stand, codeblocks isn't in Debian testing - if that is still the case on November 5th, it won't be in the next stable release.

It would be good to make a call on whether we're going to try to fix the run time issues with 13.12 under wx3.0, or make a package from SVN trunk (an actual release would be great, but a snapshot at a suitably stable revision would probably do). We really want to get a package uploaded and into testing sooner rather than later, so there's time to shake out issues before the freeze.

[Teodor Petrov]

I'm closing this as sort of fixed, because cb works when built with wx3.0 in current trunk and the next release should work with it. There is 15.12rc1 please test it and report any problem you encounter as new bugs. Look at wx30 label for other wx30 bugs. There are some problems with wx30, but we're trying to fix them as soon as we find them. So please report.

[Mojca Miklavec]

I wanted to try it out, but:
I don't find the source release at https://sourceforge.net/projects/codeblocks/files/Sources/
https://github.com/obfuscated/codeblocks_sf doesn't have the 2016.xx branch
* (I know I can do a SVN checkout, I just wonder why the other options don't work)

[Mojca Miklavec]

I'm unable to test because I get an error during compilation (checout from branch-16.xx), but that's probably something for a new ticket anyway:

debuggermanager.cpp:490:25: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'uint64_t *' (aka 'unsigned long long *')
    if (address.ToULong(&result, 16))
                        ^~~~~~~

A ticket is already open: https://sourceforge.net/p/codeblocks/tickets/274/

[Mojca Miklavec]

After the workaround for the above problem: when trying to exit the program I stil get:

../src/common/wincmn.cpp(478): assert "GetEventHandler() == this" failed in ~wxWindowBase(): any pushed event handlers must have been removed

Call stack:
[00] wxWindow::~wxWindow()                   
[01] wxTopLevelWindowBase::~wxTopLevelWindowBase() 
[02] MainFrame::~MainFrame()                 
[03] wxAppBase::CleanUp()                    
[04] wxApp::CleanUp()                        
[05] wxEntryCleanup()                        
[06] wxUninitialize()                        
[07] wxEntry(int&, wchar_t**)                
[08] main                                    
[09] start                                   
[10] 0x00000002 

But there is already https://sourceforge.net/p/codeblocks/tickets/162/ for that.