Author Topic: The 29 november 2006 build is out.  (Read 8428 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5149
The 29 november 2006 build is out.
« on: November 29, 2006, 10:40:18 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 29 November 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_Ubuntu6.06.deb (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_suse100+101.rpm (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_fc4+5.rpm (not yet)


Resolved Fixed:

  • Added new contrib plugin: a very simple regular expressions testbed
  • Better build-scripts error handling
  • Fixed a crash and a freeze when the symbols browser is disabled
  • Added per-project option for code-completion parser: custom parser search paths. Found in "Project->Properties"
  • fix bootstrap regexp bug affecting libtool 1.10+

Regressions/Confirmed/Annoying/Common bugs:

  • toolbar-images-not-changing-state (is a wx problem/Win XP problem)
  • menu items with icon not correctly aligned (since wx263)


Offline Methedrine

  • Multiple posting newcomer
  • *
  • Posts: 11
  • Wearing Cheap Shades
Re: The 29 november 2006 build is out.
« Reply #1 on: November 30, 2006, 01:09:56 am »
This version is somehow strange. When I start Code::Blocks it keeps on popping up the compiler-auto-detection dialog. Additonally it crashes/freezes as soon as I open a workspace or project. I guess it might be a threading-related problem considering codeblocks consumes 50% cpu time from my Core 2 Duo 6400. Anyone else with multi-core architectures experiencing this problem?
Some people get by with a little understanding, some people get by with a whole lot more ...

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: The 29 november 2006 build is out.
« Reply #2 on: November 30, 2006, 02:01:31 am »
Mac OS X 10.4: http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_macx86.zip
Now using the UNICODE version of wxWidgets 2.6 for Tiger, instead of the earlier ANSI.

Mac OS X 10.3: http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_macppc.zip
Still using the ANSI version for Panther, compiled with GCC 3.3 and might run on 10.2...

The shared library is still bundled with the application, will move to a framework later on.
« Last Edit: November 30, 2006, 08:45:53 pm by afb »

dengkie

  • Guest
Re: The 29 november 2006 build is out.
« Reply #3 on: November 30, 2006, 11:11:07 am »
Symbol browser for 3312 behaving funny.

If default workspace is loaded at startup, then symbols browser is blank. One needs to re-activate project in Manager before it refreshes properly. If not, it just stays blank.

Also, when there are no files opened in the editor, and I open a file from the Manager, Symbols Browser does not refresh to the opened file's symbols. It only starts to refresh correctly when another file is opened and I switch back to the first file. Looks like it is failing to refresh correctly each time a file is newly opened.
« Last Edit: November 30, 2006, 11:16:51 am by dengkie »

Offline nostromo

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: The 29 november 2006 build is out.
« Reply #4 on: November 30, 2006, 11:57:10 am »
Would be very nice if there was a Slackware package also.

Offline manciuleas

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: The 29 november 2006 build is out.
« Reply #5 on: November 30, 2006, 01:24:30 pm »
After you manage to compile codeblocks you can use 'checkinstall -S' to create a Slackware package. That's what I'm using.

Offline huzhongshan

  • Multiple posting newcomer
  • *
  • Posts: 109
Re: The 29 november 2006 build is out.
« Reply #6 on: November 30, 2006, 03:23:22 pm »
is there an all-in-one package for install for newbie ?
including wxwidgets(binary) mingw and the correct setting (like WXDIR )

I install the rc2 , and have to set lots of things to make it compile correctly.

I think the all-in-one package( like wxdevcpp ) will help newbies much.

Offline skirby

  • Almost regular
  • **
  • Posts: 137
Re: The 29 november 2006 build is out.
« Reply #7 on: November 30, 2006, 04:58:01 pm »
Hello,

I have a crash when I exit Code::Blocks.
I simply launch C::B.
Once launched, I exit C::B
Nothing happen but 100% CPU is used.
After 4 or 5 second, I have this error message:


I have deleted all files in C:\Documents and Settings\<MyUserName>\Application Data\codeblocks and restart C::B but when I exit C::B I have the same problem.

For information, I am using Windows 2000 sp4 and this nightly build.

What do you need in order to reproduce this behavior (any config files ?)

Thanks and have a nice day.

Offline nostromo

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: The 29 november 2006 build is out.
« Reply #8 on: November 30, 2006, 05:36:32 pm »
After you manage to compile codeblocks you can use 'checkinstall -S' to create a Slackware package. That's what I'm using.


That is not a problem, I'm already using it but, as you know I'm having great difficulties building C::B.
I never had so much trouble compiling software in Slackware and the reason why am I using this distro
is because everything goes quite easy with it regarding libs and other configurations.
Previously I used Mandriva but it turned out it's dependency hell when it comes to installing
software that is not supporting this distro, same is with other rpm based distros.

djeffdionne

  • Guest
Re: The 29 november 2006 build is out.
« Reply #9 on: December 13, 2006, 07:24:37 am »
Mac OS X 10.3: http://prdownload.berlios.de/codeblocks/CB_20061129_rev3312_macppc.zip
Still using the ANSI version for Panther, compiled with GCC 3.3 and might run on 10.2...

Hello All,

Since this is my first post, thank you to everyone working on Code::Blocks!

I tested this build for Mac PPC (the newest one on Berlios as of today) and I have
a few bugs to report:

1. The wizard for creating a console application seems to try and create directories
off of / (likely the CWD) and this fails unless the path is edited manually.

2. xterm is used by default for the console terminal window.  This doesn't work if
the C::B is launched from Finder (which it will be)

3. The Watch window seems to work in basic tests, but moving it around to dock it
causes large areas of the screen to be corrupted until it actually does dock. (FYI
G4 iBook, Video Chipset Model:   ATY,RV280M9+)

4. When GDB exits, the process isn't reaped and stays as a zombie.  C::B then
can't build the project or even exit cleanly

5. Some of the fonts are strange sizes.  In the Messages notebook, Code::Blocks tab,
fonts are unreadiby small.  In File->Properties Properties tab, numbers are HUGE...
maybe 40-50 pixels high!

UI nits:

Toolbars seem a little too thin, they run together one on top of the other and Splash
Screen isn't centered :^)

Cheers, we'll test more and on Linux and Win in the next few days as well.
J.

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: The 29 november 2006 build is out.
« Reply #10 on: December 13, 2006, 10:15:49 pm »
Since this is my first post, thank you to everyone working on Code::Blocks!

Welcome! :-)

Quote
I tested this build for Mac PPC (the newest one on Berlios as of today) and I have
a few bugs to report:

1. The wizard for creating a console application seems to try and create directories
off of / (likely the CWD) and this fails unless the path is edited manually.

None of the wizards have been edited for Mac (yet).

Quote
2. xterm is used by default for the console terminal window.  This doesn't work if
the C::B is launched from Finder (which it will be)

Known bug, but there is a patch available.

Quote
3. The Watch window seems to work in basic tests, but moving it around to dock it
causes large areas of the screen to be corrupted until it actually does dock. (FYI
G4 iBook, Video Chipset Model:   ATY,RV280M9+)

This is an upstream issue with wxFNB I think.

Quote
4. When GDB exits, the process isn't reaped and stays as a zombie.  C::B then
can't build the project or even exit cleanly

Believe it or not, it used to be even worse :-)

Waiting for the wxExecute drop/rewrite, I guess.

Quote
5. Some of the fonts are strange sizes.  In the Messages notebook, Code::Blocks tab,
fonts are unreadiby small.  In File->Properties Properties tab, numbers are HUGE...
maybe 40-50 pixels high!

Patching these, one place at a time. For now, only editor window and logs are fixed.

Quote
UI nits:

Toolbars seem a little too thin, they run together one on top of the other

Hmm, I don't recall this but you could be right.

Quote
and Splash Screen isn't centered :^)

Sigh, I just knew someone would notice this :-)

Quote
Cheers, we'll test more and on Linux and Win in the next few days as well.
J.

The other platforms are a bit (read as: a lot) more mature.

But you can also run wxGTK using X11.app, if you like to...