User forums > Nightly builds

The 29 July 2006 build is out.

(1/3) > >>

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://prdownload.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://prdownload.berlios.de/codeblocks/mingwm10.7z

For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb_wx2.6.3p2.7z

The 29 July 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20060729_rev2796_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_200600729_rev2796_Ubuntu6.06.deb
         http://prdownload.berlios.de/codeblocks/CB_20060729_rev2797_fc4+5.rpm


Resolved Fixed:


* some little include fixes and const adjustments (plugin manager and configuration)
* Removed "changes take effect on restart" alert.
* KeyBinder v0.4.23 reverted to v0.4.20 (cb 2761) because of exit crashes
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:
people suffering from the crashes that seemed to be related to the keybinder, could you please redo your tests. Those crashes should be gone now (let's hope they are  ;-)  )

lubos:
horaaaaaaaaaaaaaaaaaaay :lol: :lol: :lol:
good work

k1mgy:
Thanks for this build. 

Please remember that annoying lack of keypad navigation response.  It's driving me nuts.  If there's anything I can contribute to fixing it let me know (I might break something else in the process, but am willing to try).

/m

marfig:
Are there any plans on upgrading the debug pluggin? Specifically, having it mirror every gdb output?

While debugging with conditions set on my breakpoints I was led to believe the pluggin was not working because the debugger would stop at the breakpoint even when it shouldn't (e.g. the condition evaluated to false). It was only when I went to my console and debugged manually, I realized my condition was not being evaluated because it was depending on an inlined function.

On these cases GDB outputs:

--- Quote ---Error in testing breakpoint condition:                                                                 
Cannot evaluate function -- may be inlined
--- End quote ---

It would be really helpful if at least this output was mirrored by the pluggin.

Navigation

[0] Message Index

[#] Next page