wxSmith only for wx28 anymore

[killerbot]

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]

[Morphius Faydal]

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]

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.

[MortenMacFly]

Should we switch CB itself to wx28 only anymore ? [then we can update wxFlatNotebook]

Did you read this: http://forums.next.codeblocks.org/index.php/topic,6349.msg48732.html ?
I would have nothing against wx28 since I remained on wx26 on purpose to ensure backward compatibility. So far there was always a way to support both versions - recent non-wx26 compatible changes Byo fixed easily. So he can do with this one: only comment out the four lines in question and that's it.
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.

[stahta01]

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

[Morphius Faydal]

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

[stahta01]

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

[Morphius Faydal]

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

Oh.

[byo]

Hi
I couldn't answer ealier, have limited access to the Internet.
Sorry for breaking wx 2.6 build. I forgot about this option.
It's rather hard for me to test wx 2.6 (I compile sources using wx 2.8 in PCH and non-PCH mode which is already time-consuming), so can anybody check whether there are some other files which doesn't compile on 2.6?

BYO

[MortenMacFly]

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... ;-)

[Alturin]

...
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?

[Morphius Faydal]

...
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?

FC I think we can get away with... Gentoo is still wx263, you need to manually install the wx284 ebuilds... But if we provide an ebuild for the C::B nightly, then we can just point to the bugzilla.gentoo for the wx284 ebuilds... This being a development release, we can expect a gentoo user to know how to create an overlay and put in their own ebuilds, right?

[tvaster]

Here is an error:

Suse 10.2

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'       

wxWidgets-2.8.4           --enable-compat26
svn 4235 codeblocks      --enable-contrib

Fred V                                                     

[Biplab]

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’       

Why are you using UNIVERSAL build of wxWidgets?? :shock:

To compile C::B without any error, please configure wxWidgets as (an example)-

Code Select Expand

./configure --disable-debug --enable-shared --enable-unicode --enable-monolithic --with-gtk=2

Please do not use Universal and X11 build of wxWidgets. Use wxGTK build instead.

Edit 1:
Please don't post off-topic. The error you've posted is not related with the topic that is being discussed here.

[tvaster]

Sorry, newbie.  Where should it be posted?

Everything compiles well now.  Thanks.

However when starting C::B I get a scroll-up message stating that there is a problem with "libwxsmith.so"  and "libwxsmithcontribitems.so",
and a second scroll-up stating that wxSmith may not be of the same version. All was just compiled, including wxWidgets-2.8.4 as suggested.  I patiently waited for a Suse 10.2 RPM but now have resorted to scroll my own to use wxSmith.

Hope this one is not off-topic.

Fred V

[Biplab]

Please post such requests in "Help" section of forum.