Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on November 20, 2006, 09:44:12 pm

Title: The 20 november 2006 build is out.
Post by: killerbot on November 20, 2006, 09:44:12 pm
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 20 November 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20061120_rev3245_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20061120_rev3245_Ubuntu6.06.deb (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061120_rev3245_suse100+101.rpm (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061120_rev3245_fc4+5.rpm (not yet)


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 20 november 2006 build is out.
Post by: afb on November 20, 2006, 10:52:23 pm
  • prefix finding bugfix
  • ...
  • Relocation fixes

Unfortunately those two kinda cancelled each-other out, on Mac OS X.
Fixed one, broke another. Oh well, we'll get the new one next time... :-)

But for now it looks in SharedSupport instead of Resources as it should.
Title: Re: The 20 november 2006 build is out.
Post by: keenblade on November 21, 2006, 05:37:25 am
If I close the workspace within file menu or within Projects pane by right click and click "Close workspace", then the Code::Blocks itself exits.
This only occures with the vcfAllProjects.workspace of VCF. Also it is the same for some other workspaces from VCF.
It is reproducable everytime.
This is not specific to my Code::Blocks rev:3248 windows svn build. Also all the earlier revisions I tried have this bug.
Title: Re: The 20 november 2006 build is out.
Post by: tom0769 on November 21, 2006, 11:21:20 am
Hi,
where can I get the latest ANSI built?
The unicode built does not work on win me.
Title: Re: The 20 november 2006 build is out.
Post by: killerbot on November 21, 2006, 12:38:50 pm
check the nightly build posts, from time to time Seth has replied with a download link of his ansi build
Title: Re: The 20 november 2006 build is out.
Post by: gjsmo on November 21, 2006, 02:14:11 pm
Don't know if this has been fixed, but if I minimize C::B for more than about a minute, I can't get it back up. This is very annoying, but I think an autosave feature would help.
Title: Re: The 20 november 2006 build is out.
Post by: MortenMacFly on November 21, 2006, 08:27:52 pm
but I think an autosave feature would help.
Ever had a look into the environment settings -> the autosave plugin? ;-)
Title: Re: The 20 november 2006 build is out.
Post by: gjsmo on November 22, 2006, 12:23:32 am
but I think an autosave feature would help.
Ever had a look into the environment settings -> the autosave plugin? ;-)
Never noticed it - that's relatively new I think.

EDIT:I still don't like it freezing.
Title: Re: The 20 november 2006 build is out.
Post by: Alturin on November 23, 2006, 07:02:20 am
Are you sure it's "freezing"? Does windows give the [program doesn't respond] tag thing?
You could try to (manually, so not using windows-d or similar shortcut) minimizing all other programs; I had something similar before with another program, and that way it'd be accessible again. Might be that it's not really a C::B bug, but more of a annoying combination of circumstances?
Title: Re: The 20 november 2006 build is out.
Post by: gjsmo on November 25, 2006, 12:30:22 am
Are you sure it's "freezing"? Does windows give the [program doesn't respond] tag thing?
You could try to (manually, so not using windows-d or similar shortcut) minimizing all other programs; I had something similar before with another program, and that way it'd be accessible again. Might be that it's not really a C::B bug, but more of a annoying combination of circumstances?
I've tried everything I can think of. I've closed almost all my processes and it still is frozen. But maybe I'm just unlucky.
EDIT: All my processes except those crucial to Windows.