User forums > Nightly builds
The 20 June 2006 build is out.
killerbot:
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z
For support of ansi builds, a link to the ansi windows wxWidget dll (2.6.2) for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z
The 20 June 2006 build is out.
- Windows : http://download.berlios.de/codeblocks/CB_20060620_rev2586_win32.7z
- Linux :
http://download.berlios.de/codeblocks/CB_20060620_rev2586_Ubuntu6.06.deb
http://download.berlios.de/codeblocks/CB_20060620_rev2586_fc4+5.rpm
Resolved Fixed:
* CB-tris : Added base class for game window & Added more sophisticated back-to-work-timer
* improved BCC compiler options (thanks to Nils)
* CB-tris : fixed automake issue that caused broken compilation under linux
* Updated byogames to work on linux
* updated profiler to look inside project's working dir for gmon.out, too (incl. minor code cleanup)
Regressions/Confirmed/Annoying/Common bugs:
* toolbar-images-not-changing-state (is a wx problem/Win XP problem)
* there are several issues with Code Completion (is being redesigned : work in progress)
* menu items with icon not correctly aligned (since wx263)
killerbot:
this has came up in previous discussion, but i can confim the "whooaah" crash dialog popping up, and choose abort allows to continue whithout any problems. Each time it happened to me when I wanted to insert (paste) something in #include sections of a .cpp file
oz:
--- Quote from: killerbot on June 20, 2006, 06:55:20 pm ---Resolved Fixed:
* Updated byogames to work on linux
--- End quote ---
It still could not work well, same as before. fedora core 5. please take a look.
--- Quote ---this has came up in previous discussion, but i can confim the "whooaah" crash dialog popping up, and choose abort allows to continue whithout any problems. Each time it happened to me when I wanted to insert (paste) something in #include sections of a .cpp file
--- End quote ---
That heppened under WinXP sp2, when I click project->open project, or file->open, also happend when I choose the directory. if I click 'Abort' two or three times, it CB will work as normal, click 'Retry' will remain that dialog box, click 'Ignore' will keep that dialog box too, but the violation address will be 0, and each time increased by 2.
[attachment deleted by admin]
killerbot:
--- Quote from: killerbot on June 20, 2006, 11:29:23 pm ---this has came up in previous discussion, but i can confim the "whooaah" crash dialog popping up, and choose abort allows to continue whithout any problems. Each time it happened to me when I wanted to insert (paste) something in #include sections of a .cpp file
--- End quote ---
had it again today (rev 2586) when I wanted to print something. Click 5 times abort, press the print button again, again 5 aborts, press print button again --> printing :-)
byo:
--- Quote from: oz on June 21, 2006, 03:46:23 am ---It still could not work well, same as before. fedora core 5. please take a look.
--- End quote ---
Ok, give me one more try :) I'll try to fix that for sure. In fact I know where is the problem but because it didn't occured in gentoo I thought it was fixed.
--- Quote ---
--- Quote ---this has came up in previous discussion, but i can confim the "whooaah" crash dialog popping up, and choose abort allows to continue whithout any problems. Each time it happened to me when I wanted to insert (paste) something in #include sections of a .cpp file
--- End quote ---
That heppened under WinXP sp2, when I click project->open project, or file->open, also happend when I choose the directory. if I click 'Abort' two or three times, it CB will work as normal, click 'Retry' will remain that dialog box, click 'Ignore' will keep that dialog box too, but the violation address will be 0, and each time increased by 2.
--- End quote ---
Hmm, It seems like new exception handler is the cause. If anyone has debugged C::B before, exceptions were thrown when opening files or selection directories but previous exception handler did not threat them as fatal. I guess these exceptions may be some additional handlers installed in system (may be tortoise or something)
Navigation
[0] Message Index
[#] Next page
Go to full version