due to last nights commit for wxsToolbar, it only builds with wx28.
Is that intentional ?
If so : can all core developers live with this ?
Should we switch CB itself to wx28 only anymore ? [then we can update wxFlatNotebook]
Should we switch CB itself to wx28 only anymore ? [then we can update wxFlatNotebook]Did you read this: http://forums.codeblocks.org/index.php/topic,6349.msg48732.html ?
Considering that everyone says you HAVE to use wx 2.8.4 due to bugs in 2.6.3, I'm surprised you haven't gone 2.8-only already.
Considering that everyone says you HAVE to use wx 2.8.4 due to bugs in 2.6.3, I'm surprised you haven't gone 2.8-only already.
I think most people are saying use wx 2.8.4 because of all the bugs in wx 2.8.3.
Tim S
Considering that everyone says you HAVE to use wx 2.8.4 due to bugs in 2.6.3, I'm surprised you haven't gone 2.8-only already.
I think most people are saying use wx 2.8.4 because of all the bugs in wx 2.8.3.
Tim S
I could swear I've seen a bunch that say upgrade to 2.8.4, because some things don't work right in 2.6.3
Considering that everyone says you HAVE to use wx 2.8.4 due to bugs in 2.6.3, I'm surprised you haven't gone 2.8-only already.
I think most people are saying use wx 2.8.4 because of all the bugs in wx 2.8.3.
Tim S
I could swear I've seen a bunch that say upgrade to 2.8.4, because some things don't work right in 2.6.3
There are some things that work better in wx 2.8.4, but most of them are not items considered bugs in 2.6.3.
Bugs implies they were supposed to work in 2.6.3. Many things on Macs never worked right in 2.6 branch and where never claimed to work right for Macs, that are claimed to work somewhat at least in 2.8 branch.
Tim S
so can anybody check whether there are some other files which doesn't compile on 2.6?That's the only one - I only compile in wx26, so I can easily tell... ;-)
...
I think so far one of the main drivers to keep wx26 compatibility was because wx284 (which fixes serious bugs) was not available on all (Linux) platforms. I don't know how the status is now.
With regards, Morten.
...
I think so far one of the main drivers to keep wx26 compatibility was because wx284 (which fixes serious bugs) was not available on all (Linux) platforms. I don't know how the status is now.
With regards, Morten.
wxWidgets provides the debian/ubuntu package on their website.
Maybe we could do a poll and see how many users do not have wx provided by them by their distro?
And ofcourse we could consider providing a binary ourselves for Gentoo/FC and the other builds that we have nightlies for?
g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/include -I/usr/local/lib/wx/include/x11univ-ansi-release-2.8 -I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXUNIVERSAL__ -D__WXX11__ -pthread -I../../../src/include/wxFlatNotebook/include -Ulinux -Uunix -O2 -ffast-math -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT renderer.lo -MD -MP -MF .deps/renderer.Tpo -c src/wxFlatNotebook/renderer.cpp -fPIC -DPIC -o .libs/renderer.o
../../../src/include/wxFlatNotebook/include/wx/wxFlatNotebook/wxFNBDropTarget.h:75: error: invalid use of undefined type ‘struct wxDropTarget’
/usr/local/include/wx-2.8/wx/window.h:60: error: forward declaration of ‘struct wxDropTarget’
./configure --disable-debug --enable-shared --enable-unicode --enable-monolithic --with-gtk=2