The 06 December 2007 build (4711) is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx287.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc421.7z

The 06 December 2007 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20071206_rev4711_win32.7z
  - Linux :
   none

Resolved Fixed:

• CodeSnippets 1.2.108 2007/12/02
  - force close of xml in OnRelease() (Closing window causes crashes)
  - immediately delete canceled "New category" & "New snippet" items, ignore filelinks in canceled properties. Avoids unnecessary "delete?" dialog.
  - fix macro substitution in CheckForMacros() broken by mod 99

Regressions/Confirmed/Annoying/Common bugs:

• toolbar-images-not-changing-state (is a wx problem/Win XP problem)

[kurapix]

Here is the build for Ubuntu 7.10 i386 - Gutsy Gibbon : download.

By the way, I'd like to say that I've just started working on updating my building script for Code::Blocks (I don't garantee anything about delay ...).

Thank you for the devs for their great work, you rocks!!! Keep it that way.

Kurapix

[orefa]

The message pane hides correctly now if there is no compilation error, thanks for this fix.

The pane still doesn't show on compile as before, to provide visual feedback that something is indeed happening and to show progress. Maybe the "View" settings needs an "Auto-show on compile" check box for this, although I don't remember seeing something like this in past versions when it used to behave smoothly all around...

[pasgui]

Build for Ubuntu i386 can be found here

Best regards, pasgui

[Rye]

I'm having a problem with compiling projects in C::B since i updated to revision 4711 today.

Every time i compile i get 'obsolete option' messages for every source file (as shown below) and allot of my include paths are not being added.

Code

Compiling: ../../Source/Interfaces/Interface.Audio.cpp
cc1plus: note: obsolete option -I- used, please use -iquote instead
Compiling: ../../Source/Interfaces/Interface.IO.cpp
cc1plus: note: obsolete option -I- used, please use -iquote instead

I don't really understand this message and there are no compiler options in the project build options that look like -I-, i do however have alot of -I/usr/include styled options though, but that can't be obsolete can it? Also i don't understand this -iquote business. :S

Anybody know what happened, it was working fine in C::B revisions prior to 4700 and i haven't updated or changed any compiler tools to my knowledge so it must be something to do with my project build setup in C::B.

[TDragon]

This happens when you choose to have your PCH (precompiled header) generated in the object output directory instead of one of the other two options. See your project properties dialog.

[Rye]

Ah legend, that fixed it ... though i still don't know why that option changed as i sure didn't touch it. :S
Thanks anyway.

[Biplab]

Code

Compiling: ../../Source/Interfaces/Interface.Audio.cpp
cc1plus: note: obsolete option -I- used, please use -iquote instead
Compiling: ../../Source/Interfaces/Interface.IO.cpp
cc1plus: note: obsolete option -I- used, please use -iquote instead

I don't really understand this message and there are no compiler options in the project build options that look like -I-, i do however have alot of -I/usr/include styled options though, but that can't be obsolete can it? Also i don't understand this -iquote business. :S

Anybody know what happened, it was working fine in C::B revisions prior to 4700 and i haven't updated or changed any compiler tools to my knowledge so it must be something to do with my project build setup in C::B.

It happens because C::B can't detect the GCC version due to some reason. Otherwise (if the version is detected properly) C::B can handle this.

[Morphius Faydal]

Where can I get wxGTK 2.8.7 for Ubuntu "Gutsy"?  Neither one of the repos on the wiki even *has* gutsy.

[JGM]

Where can I get wxGTK 2.8.7 for Ubuntu "Gutsy"?  Neither one of the repos on the wiki even *has* gutsy.

I don't know if the official repos of gutsy already have it (you should do a search on synaptic or sudo apt-get upgrade), but if not over here:
http://wiki.wxpython.org/InstallingOnUbuntuOrDebian

[cacb]

Where can I get wxGTK 2.8.7 for Ubuntu "Gutsy"?  Neither one of the repos on the wiki even *has* gutsy.

Hi,

I have installed wxWidgets 2.8.7 on Gutsy i386 by adding in Adept Manager repositories
http://apt.wxwidgets.org/ gutsy-wx main

There is a key at http://apt.wxwidgets.org/key.asc

wxWidgets works fine on Gutsy, although I have not tried C::B on Gutsy yet.

[Jenna]

I just added svn4713 to my repo (see sig).

The changes since svn4711 can be seen here.

The update is a little late, but I haven't been at home this week, because of work, and there was no internet-connection in the hotel.

Sorry for the inconvenience.

[hollingsworthd]

So are you not building for linux anymore?

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx287.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc421.7z

The 06 December 2007 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20071206_rev4711_win32.7z
  - Linux :
   none

Resolved Fixed:

• CodeSnippets 1.2.108 2007/12/02
  - force close of xml in OnRelease() (Closing window causes crashes)
  - immediately delete canceled "New category" & "New snippet" items, ignore filelinks in canceled properties. Avoids unnecessary "delete?" dialog.
  - fix macro substitution in CheckForMacros() broken by mod 99

Regressions/Confirmed/Annoying/Common bugs:

• toolbar-images-not-changing-state (is a wx problem/Win XP problem)

[killerbot]

our linux builders have run out of spare time.
But some others mostly reply in the thread with a linux build. I will look into this, to have a it a bit more organized.

[cacb]

Thanks for the build, I do have some observations though  :lol: . Previously I have been using build 4237 on Windows XP (Using MS Visual C++ 2005 Express compiler) and build 4066 on Kubuntu with GCC compiler. I want to continue with this compiler setup, but obviously upgrade to a more recent version of Code::Blocks.

My project is set up using 4 build targets, i.e. W32_Release and W32_Debug, plus UX_Release and UX_Debug. W32 means MS Visual C++ 2005 build, UX means Linux GCC build here.

Problem 1
I found that there is sometimes a bug in C::B when selecting among such build targets. If I select the build target UX_Debug using the "Build Target" combo in the toolbar, I get an error message box saying "This target is configured to use an invalid debugger. The operation failed....". I notice that when starting the debugger (Debug -> Start) there is a message in the Debugger window
Selecting Target
W32_Debug    <= Wrong!, I had UX_Debug selected.

If I instead select the build target by first selecting via the menu option Build -> Select target ->  UX_Release, then switch back Build -> Select target ->  UX_Debug, then debugging works properly! So it seems to me that selecting build targets via the menu vs. using the toolbar combo does not do the same thing. That looks like a bug to me.

Problem 2
Another issue is when I open my project on Linux, I am faced with a "Compiler selection" dialog that says "The defined compiler for W32_Debug cannot be located (ID: msvc8). Please choose the compiler you want to use instead and click OK". Obviously this makes little sense. The compiler setting for that build target is correct, but the build target is not in use at all on Linux! Is there a way to switch off this message? It was not a problem with the older C::B and I don't think build 4711 on Windows complains in the same way for my UX_Debug build target. Any advice?

Anyway I am really happy that Debugging on Linux seems to work fine  , I had problems with that before.

[killerbot]

Problem 2
Another issue is when I open my project on Linux, I am faced with a "Compiler selection" dialog that says "The defined compiler for W32_Debug cannot be located (ID: msvc8). Please choose the compiler you want to use instead and click OK". Obviously this makes little sense. The compiler setting for that build target is correct, but the build target is not in use at all on Linux! Is there a way to switch off this message? It was not a problem with the older C::B and I don't think build 4711 on Windows complains in the same way for my UX_Debug build target. Any advice?

That's a bug, normally it should shut up about it, and during the build step tell that compiler is not available/installed and skip that target.

I have similar projects with every target being build with a different compiler (total of 8 different compilers).

I will investigate in future. Thing is this happens only on linux, on windows it's no problem (there when one of my compilers is missing it just skips that target).

[cacb]

That's a bug, normally it should shut up about it, and during the build step tell that compiler is not available/installed and skip that target.

I have similar projects with every target being build with a different compiler (total of 8 different compilers).

I will investigate in future. Thing is this happens only on linux, on windows it's no problem (there when one of my compilers is missing it just skips that target).

Thanks for looking into it . C::B is such a nice IDE, so if that linux compiler selection issue can be fixed it will be much easier to upgrade. I want to be able to use the same build for both Linux and Windows.

Btw. problem 1 was poorly described. The message appears when trying to start start the debugger. I do think there is a bug related to how the build target is selected. I suspect they have different event handlers.

[deadneurons]

Hi,
I'm experiencing crashes when saving projects after deleting or renaming a target.

'just want to add my observation. :idea:


EDIT:  It appears that it only affect the saving if I'm using a custom makefile, no need to change or
rename the target since it's not use?
EDIT2: I posted too fast, it's the same problem as first stated. sorry.

[wobien]

At last i found out what caused the crashes on close workspace i was still having.

(I have a workspace with 2 projects, a app project and a static library, and my problem was that when code completion is enabled, C::B crashes when i close the workspace)

I experimented with a new workspace, with 2 new projects.
In the projects i gradually added  the files of my old projects, until the new workspace crashed on close.
The file that caused the crash is a class definition file and the class in this file has the same name as a class in the library. The class in the library is in an other namespace, so this should be no problem.
It seems to be a problem for the code completion, causing the crashes.
I renamed the class in the app project, and the problems have gone!
wobien

[Jenna]

At last i found out what caused the crashes on close workspace i was still having.
I experimented with a new workspace, with 2 new projects.
In the projects i gradually added  the files of my old projects, until the new workspace crashed on close.
The file that caused the crash is a class definition file and the class in this file has the same name as a class in the library. The class in the library is in an other namespace, so this should be no problem.
It seems to be a problem for the code completion, causing the crashes.
I renamed the class in the app project, and the problems have gone!
wobien

I just posted another solution for this (or a similar) problem.
It's a bug int the "debuggergdb.cpp".
Look here

[AmR EiSa]

Where can I get wxGTK 2.8.7 for Fedora 8 and C::B build ?

[MP2E]

Hello, I'm new here. However, since I like this project, I've taken upon myself to compile the nightly builds and package them for Slackware. Here is this nightly build for Slackware(i386):
http://www.savefile.com/files/1251920
Here is my project page so you can see my future compiled nightlies:
http://savefile.com/projects/808576591

Since Slackware was developed closely to linux, it's almost a "Vanilla" port, meaning Code::Blocks compiled for Slackware will most likely run on other Distro's with no issues. If you're using a different distro, just know that Slackware packages are GZipped with an install directory added on. So installing is really simple, just UnTar it then delete the install directory.

[Rayman]

For me, the 'Auto-hide message pane' function now works as expected! Thanks for fixing this.