News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

The 01 June 2006 build is out.

Started by killerbot, June 01, 2006, 08:44:39 PM

Previous topic - Next topic

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.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

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.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 for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 01 June 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060601_rev2520_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060601_rev2520.deb (not yet)
         http://download.berlios.de/codeblocks/CB_20060601_rev2520_fc4+5.rpm


Resolved Fixed:


  • Fixed bug #7707 which happened to be a problem with wxWidgets when reading a hexadecimal number using wxString::ToLong and that number was a negative one
  • Decided to replace the call to wxString::ToLong to a handwritten wxStrHexTo<T> reading from the second match (this fixes a minor bug that could arise with the previous fix)
  • Updated std::string evaluation in GDB's script

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)


asdf

#1
I'm using visual express compiler with codeblocks, how come when I try to compile a file without it being in a project, it returns errors in the iostream header file...?

also, would it be too much trouble to provide an icon association to Visual Studio 2005 Solutions and Projects???

Phoenix

#2
I have a problem wxSmith. When you move project into different folder and you where unfrotuned to leave full path (drive+folders+file) instead of relative you can't do anything. C::B is displaying "Can't load image from..." and the only way to close it down is to ether create missing file in specified path or to kill C::B. I have noticed that when you select file for the first time it has relative path, but after selecting different control and moving back to wxStaticBitmap you can see full path.

[edit]And one more thing: You CAN NOT type in path manually. You have to use "Browse" and you are not able to put relative path.[/edit]

I'm using latest nightbuild.

MortenMacFly

Quote from: asdf on June 02, 2006, 07:14:37 AM
how come when I try to compile a file without it being in a project, it returns errors in the iostream header file...?
A single file is usually compiled with the default compiler which must not be Visual C++. I know you can setup any compiler as default, but there are cases where "gcc" is setup as default anyway - like single file compilation. I've noted this already, and I'm already looking into this to file a patch...
To setup a specific compiler put the file in a project.
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

Jewe

Hi,

I had a question regarding the usage of the help files.
Could be that its done by design or its just a defect.

what do I do?
Type wxsocketbase then right mouse click "Locate in WX"
WX is the name I gave to the wx help file.

So far everythings great, nice feature.
But then I want to return to Codeblocks and I need to close the help file.?  :shock:

Is this done by design?

Regards,

Jewe
Anything curved in the hardware can be straighten with software :D
OS: Vista64 + Debian(to play with)
Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

bSr43

Hi !

Code::Blocks is simply GREAT, and I'd like to thanks all the people behind this project !

Just a little information : I tried this build (Fedora package) and saw that /usr/share/codeblocks/scripts was not in the archive, so when I debug something, I've a message that warns me about a missing gdb_types.script file.

I've checkout a fresh version, and then copy the scripts directory into the expected location, and now all is alright.

So, could you please add those files to the RPM archive for future version ?

Ceniza

Quote from: JeweSo far everythings great, nice feature.
But then I want to return to Codeblocks and I need to close the help file.?

It's a known issue and it's related to the opening of CHM files itself.

Every program that opens a CHM file looking for a keyword will have that behaviour. Just blame MS on this one :)

TheTuxKeeper

Quote from: bSr43 on June 02, 2006, 02:11:38 PM
Hi !

Code::Blocks is simply GREAT, and I'd like to thanks all the people behind this project !

Just a little information : I tried this build (Fedora package) and saw that /usr/share/codeblocks/scripts was not in the archive, so when I debug something, I've a message that warns me about a missing gdb_types.script file.

I've checkout a fresh version, and then copy the scripts directory into the expected location, and now all is alright.

So, could you please add those files to the RPM archive for future version ?
The script files will be there in today's nightly RPM ;)

Thank you for reporting it :D
Nightly builds for openSUSE