Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: Biplab on March 20, 2007, 06:28:34 pm
-
Hello Everybody,
wxWidgets team has released wxWidgets-2.6.4 today. Still an official announcement has not been made. But the tarballs are available from:
http://biolpc22.york.ac.uk/pub/2.6.4/
I'm yet to compile Code::Blocks with it. I'll post the results after some time.
Regards,
Biplab
-
Code::Blocks compiles without any problem. :D
-
FYI:
That ftp site is where they asked the people to verify it before putting it on sf.net.
So, it should be out tomorrow on sf.net unless a major problem is found.
Tim S
-
Yes Tim, you're correct. :)
I think they will upload it soon to Sourceforge.
http://article.gmane.org/gmane.comp.lib.wxwidgets.devel/84491
Though I could not find WX_2_6_4 branch in CVS. :)
Regards,
Biplab
-
@Tim, does this wx2.6.4 contain all our backported fixes ??
I hope so, then we can fall back on the regular dll (which I will build then asap).
-
I am compiling C::B now against the trial 2.6.4. Note, they are doing a second trial run, they missed updating the version number to 2.6.4 on the first one. Mine says 2.6.4 so it must be the second trial run.
It looks like all three patches are there. I would wait till you can download it from sf.net.
Tim S
-
@Killerbot,
This contains backported fixes. I have tested it and menu related problems are gone. Though Save button in Toolbar problem remained same.
wx 2.6.4 contains one more backported fix which will enable wxLaunchDefaultBrowser() in Linux. One user had recently filed one bug report in Berlios which will get fixed with the newer version of wx.
But as Tim said, you can wait till it is released in Sourceforge.
Regards,
Biplab
-
so we might once again patch it ourselves ;-)
-
so we might once again patch it ourselves ;-)
Yes, if needed! :)
-
Though Save button in Toolbar problem remained same.
Biplab
The "Save button in Toolbar problem" was NOT fixed by my back-ported patches applied to our own version of 2.6.3, I still don't know where the cause for it is. Note, the problem I see with it is the "Save button" is never grayed out when it is disabled. Note, some other buttons show the same problem, but the "Save button" shows it in both size of buttons the others seem to only show it in the large 22x22 size buttons.
Tim S
-
I've noticed this bug for Print icon, too. But your menu related fixes are already available in wx-2.6.4. :)
BTW, they didn't backport couple of fixes to WX_26_BRANCH. Honestly I'm not sure which are those fixes, but I read it somewhere in the mailing list.
I don't know why they didn't tag the CVS files so far.
Regards,
Biplab
-
I think they tag it right after the upload to sf.net.
Tim S
-
FYI:
2.6.4 is on sf.net, no sign of CVS Label for 2.6.4 being created.
Tim S
-
Thanks for the info. :)
-
note : on the wx download page this is the actual link when you want the zip version for windows :
http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3.zip
this is off course incorrect, I think it is (and it does exist ;-) ) :
http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.4.zip
-
They didn't update the wx download page. Correct link is:
http://downloads.sourceforge.net/wxwindows/wxMSW-2.6.4.zip?modtime=1174484960&big_mirror=1
Or download the big daddy from:
http://downloads.sourceforge.net/wxwindows/wxWidgets-2.6.4.tar.bz2?modtime=1174482857&big_mirror=1
:)
-
download page is up to date, only the windows zip link is not correct
Current Stable Release: 2.8.2
Previous Stable Release: 2.6.4
-
Ok, Now I can see updated download page and the problem. ;)
Edit 1: I've posted one email in the wx-dev mailing list stating this problem. Hopefully they will fix it soon. :)
-
I am a beginner of C::B, and downloaded wxWidgets 2.8.3 tonight. But I couldn't know how to use it.
-
You have downloaded wxWidgets source. You need to compile it first.
Then Fire up wxWidgets Project wizard (File > New > Project menu) and follow the instructions.
If you're still not sure, please start a new thread.
-
You have downloaded wxWidgets source. You need to compile it first.
Then Fire up wxWidgets Project wizard (File > New > Project menu) and follow the instructions.
If you're still not sure, please start a new thread.
Thank you!
I have compiled it successfully. Unfortunately,there ere some other errors. I have download The 21 March Nightly Build and update it correctly,but when I launch C::B ,it always notifies me that some plugin resource, such as cbprofiler.zip,compilergcc.zip,debugergdb.zip and pluginwizard.zip, not be found. Where can I get them?
-
They come with each nightly packages. I think you've overwritten the RC2 folder with a latest nightly or so.
Just wait for next nightly. It'll be released within a day. Download it and extract the contents to a new folder.
That would solve your problem.
-
They come with each nightly packages. I think you've overwritten the RC2 folder with a latest nightly or so.
Just wait for next nightly. It'll be released within a day. Download it and extract the contents to a new folder.
That would solve your problem.
no, somebody told me to overwritten the RC2 folder but I didn't . I just copied those Nightly Build files absent in my computer to the RC2 folder, then C::B raised those errors.
BTW: how to make it work correctly if I do extract the contents to a new folder? Thank you in advance!
-
I just copied those Nightly Build files absent in my computer to the RC2 folder, then C::B raised those errors.
That's what I meant by overwriting. The main problem is RC2 is pretty old and there are couple of changes made to C::B's core. So uninstall RC2 files first before installing a newer nightly.
-
I'v uninstalled RC2,aha
Does it mean that I should install MinGW manually if I use Nightly Build ?
-
Yes! You need to install MinGW manually. And another point, if you face further problems, please start a new thread (post). Don't attach your queries to this post.
-
Yes! You need to install MinGW manually. And another point, if you face further problems, please start a new thread (post). Don't attach your queries to this post.
ok, thank you very much