Code::Blocks Forums

User forums => General (but related to Code::Blocks) => Topic started by: momaa on September 13, 2006, 01:11:22 pm

Title: Compile & run C::B on wxWidgets 2.7
Post by: momaa on September 13, 2006, 01:11:22 pm
Hello,

Is it possible to compile Code::Blocks IDE (itself) with the wxWidgets 2.7 library on Linux.
Has anybody done it?   Any difficulties with the C::B + wxWidgets 2.7.0 ?

wxWidgets 2.7.0 is the current test release.
http://wxwidgets.org/downloads/

My system is:
Ubuntu Linux 6.06.1,  32bits PC.

Regardless of the answers, I will make a try ;-)
Title: Re: Compile & run C::B on wxWidgets 2.7
Post by: David Perfors on September 13, 2006, 01:29:01 pm
As far as I know it is not yet tested with success, at least not on Windows. And because wx2.7 is the unstable release, the development team is not supporting it. When wx 2.8 is out, I think the team starts with testing that version, but that could take a year (or more I think)
Title: Re: Compile & run C::B on wxWidgets 2.7
Post by: momaa on September 13, 2006, 01:39:28 pm
Ok, the wx 2.8 (even number) will be the stable release.

I made a test and the compilation of C::B with wx2.7 headers failed.

./sdk_events.h: In member function ‘virtual wxEvent* CodeBlocksEvent::Clone() const’:
./sdk_events.h:31: error: request for member ‘operator new’ is ambiguous
./blockallocated.h:122: error: candidates are: static void* BlockAllocated<T, pool_size, debug>::operator new(size_t) [with T = CodeBlocksEvent, unsigned int pool_size = 75u, bool debug = false]

Also similar errors on CodeBlocksDockEvent and CodeBlocksLayoutEvent classes.

The errors are too difficult for me to interpret so I will now continue with the normal wx2.6.3.

Thanks.
Title: Re: Compile & run C::B on wxWidgets 2.7
Post by: kelo81 on September 14, 2006, 01:14:24 am
That's because the new wx2.7 has changed several things in the interface; they are even implementing new features... so, it's pretty normal to get errors if you are trying to compile a wx2.6.3 application with a wx2.7 enviroment...
We'll have to be patient... the most important thing is to get the final stable version of Codeblocks with wx2.6.3. I suppose that future Codeblocks versions (after the final 1) will use wx2.8, but we'll have to wait about one year... perhaps more.  :shock: