News:

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

Main Menu

The 25 october 2006 build is out.

Started by killerbot, October 25, 2006, 08:07:52 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://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 25 October 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20061025_rev3145_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20061025_rev3145_Ubuntu6.06.deb (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061025_rev3145_suse100+101.rpm
         http://prdownload.berlios.de/codeblocks/CB_20061025_rev3145_fc4+5.rpm


Resolved Fixed:


  • updated wxFlatNotebook to it's state in cvs : improvements for our Mac users
  • (CB)Profiler : case sensitivity, and renamed to Profiler

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)


Acki

#1
If I start C::B I get this error message:
some errors have been logged during
the Code::Blocks startup process.

Please review them in the logs...

but no log file is created...

Pecan

#2
Quote from: Acki on October 26, 2006, 02:55:46 AM
If I start C::B I get this error message:
some errors have been logged during
the Code::Blocks startup process.

Please review them in the logs...

but no log file is created...

The log is on the far left within the messages window (F2). Use the small arrow on the right to assure its visibility.



dronT78

Compile errors
/usr/lib/libSDL-1.2.so.0 undefined reference to 'DirectFBCreate'
etc...
why C::B needs libSDL?

AMD64 Gentoo 2006.1
DirectFB 0.9.25.1
libSDL 1.2.11

C::B build 3146

afb

Code::Blocks is now starting to work again on the Mac,
after applying all of the latest wxFlatNotebook patches.

rev3146 should build cleanly using DarwinPorts/MacPorts,
and a "standalone" nightly build will follow later this week.

wiki: Installing_Code::Blocks_from_source_on_Mac_OS_X

afb

Quote from: dronT78 on October 26, 2006, 07:39:10 AM
why C::B needs libSDL?

I know that on some Unix platforms, wxWidgets uses SDL for sound support...
You might want to check if it is wx that links libSDL, and disable it if needed ?

wxWidgets configure:
--without-sdl

takeshimiya

Quote from: afb on October 26, 2006, 09:16:03 AM
Code::Blocks is now starting to work again on the Mac,
after applying all of the latest wxFlatNotebook patches.

rev3146 should build cleanly using DarwinPorts/MacPorts,
and a "standalone" nightly build will follow later this week.

wiki: Installing_Code::Blocks_from_source_on_Mac_OS_X

Has been solved the bug of running programs on Intel build?

afb

Quote from: Takeshi Miya on October 26, 2006, 09:28:43 AM
Has been solved the bug of running programs on Intel build?

As far as I know, no... :-(

I was just happy to finally see tabs and some content again. :-)

afb

Nope, first thing you do on Intel* still hangs Code::Blocks.
This includes: compiling a file, opening a project, etc. etc.

On the plus side, Code Completion seems to be working!
(at least it didn't hang, and even completed keywords...)

* Note that this only applies to the wxMac/Carbon version!
The wxGTK version does work fine on Intel Darwin / X11.

My suggestion is to use DarwinPorts and wxGTK for now,
if one want to use Code::Blocks rather than help debug it ?

ramguru

I got some error report at starting: "ERROR: SDK version mismatch for CBProfiler (1.10.0). Expecting 1.11.2". And yeah my main CPP file was successfully cleared (0bytes) after trying to save it!! Guess if I'm going to use this IDE again  :?

killerbot

that is because thhose CBProfiler.dll/zip are no longer needed. Just remove them from the share directory  and plugin directory.

save returning to zero length, can you reproduce this ??

ramguru

#11
Quote from: killerbot on October 26, 2006, 01:07:28 PM
...save returning to zero length, can you reproduce this ??

Yeah as many times as I wish. It's simple as that:
1. I open my recent project
2. I try to comment a few lines of code in my language (with some non ANSI characters)
3. I save my project
4. I get 0-length file

P.S. it seems only comments in my language cannot be saved (Lithuanian), comments in russian are acceptable

MortenMacFly

Quote from: ramguru on October 26, 2006, 03:27:13 PM
Yeah as many times as I wish. It's simple as that:
1. I open my recent project
2. I try to comment a few lines of code in my language (with some non ANSI characters)
3. I save my project
4. I get 0-length file
I could swear that you didn't enable the "right" format for non-ansi characters encoding, right? (Settings -> Editor -> General settings -> Default encoding). What do you expect to happen then?!
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]

ramguru

OK when I set default encoding to UTF-8 and restart IDE, no more 0-length file saving. But you should not tell me that it's not a bug, just expected behaviour.

MortenMacFly

Quote from: ramguru on October 26, 2006, 04:07:25 PM
But you should not tell me that it's not a bug, just expected behaviour.
Ok- tell me an algorithm to read your mind what encoding (out of several dozen) you'd like to have for your files and I'll implement it.
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]