Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on July 11, 2006, 08:10:28 pm

Title: The 11 July 2006 build is out.
Post by: killerbot on July 11, 2006, 08:10:28 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 (2.6.2) for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 11 July 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20060711_rev2733_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20060711_rev2733_Ubuntu6.06.deb (not this time)
         http://prdownload.berlios.de/codeblocks/CB_20060711_rev2733_fc4+5.rpm


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 11 July 2006 build is out.
Post by: skirby on July 12, 2006, 12:09:08 am
Hello,

Thanks for this new build.

I have noticed a small problem with "Digital Mars Compiler" and project wizard.
When you create a project (MS Dos or Windows), by default :

1./ "Other options" for project is defined to -Wall
2./ Release "Other options" is defined to -O2

But these options seem not to be support by "Digital Mars Compiler"
Simply delete these option and you can compile the project.

Am I wrong?
Do you think these values have to be remove from project wizard template?

Thanks and have a nice day.
Title: Re: The 11 July 2006 build is out.
Post by: mandrav on July 12, 2006, 12:14:34 am
The wizards currently support the gcc* and msvc* compilers.
It's easy to add support for more but unfortunately I didn't have the time...
I might do this tomorrow though :)
Title: Re: The 11 July 2006 build is out.
Post by: Charon on July 12, 2006, 10:17:10 am
one thing i noticed in an older version (sorry, no revision number. was about 3 weeks old) and in this actual version :
1. open any file
2. fold some functions and/or if-statements
3. press shift+f12 two times (fold all and unfold all)
4. search the folds you manually placed before
5. they are correctly unfolded, but in front of them the "+" is still shown

no idea if this is a wxScintilla-bug since i have no idea how Code::Blocks communicates with it. this happened on on a fully patched WinXP Professional.

another thing i noticed in the actual version shocked my first :
after opening Code::Blocks a small window appeared in the lower right corner of my screen. it slowly slid into the screen from the bottom, showing "information" in its title-bar and some stuff about a compiler in it.
is this intended behaviour? at first i thought i caught some adware, but after reading the text i seemed to have something to do with Code:Blocks.
i really was afraid at first :D

keep up the good work
Markus
Title: Re: The 11 July 2006 build is out.
Post by: C D Tamhankar on July 12, 2006, 12:09:31 pm
Hello,

I am new to code::blocks.
It has just what programmer expects.
I have switched over to codeblocks after trying eclipse for few weeks.

I have noticed peculiar options for codeblocks IDE.

Like Borland IDE it provides setting of compiler flags for debugger mode and release mode.
But it is also available for project level. And rightly its available on Global Compiler options screen.
My little experience tells me that project level setting is redundant as its taken care at debugger / release level options.... It confuses me.



I have downloaded  GCC4.1.x

I have modified the compiler installation directory ( in compiler- debugger option)
When I compile any source file... it fails with a message 'nothing to be done'
But when I use 'autodetect option' for compiler installation directory, it selects sub-directory of codeblocks folder. Then it compiles fine.

I have also installed MinGw 5.0.3 version but codeblocks still uses its  GCC-3.4.4 compiler shipped with RC2

How to incorporate GCC-4.1 compiler

Any plans of incorporating GCC 4.1.1 as a default compiler for 1.0-RC3 version ?

 
Title: Re: The 11 July 2006 build is out.
Post by: thomas on July 12, 2006, 12:18:42 pm
Quote
Any plans of incorporating GCC 4.1.1 as a default compiler for 1.0-RC3 version ?
No plans.
Title: Re: The 11 July 2006 build is out.
Post by: mandrav on July 12, 2006, 12:20:11 pm
Any plans of incorporating GCC 4.1.1 as a default compiler for 1.0-RC3 version ?

GCC 4.x hasn't been released for windows. How could we distribute it?  :shock:
Title: Re: The 11 July 2006 build is out.
Post by: Zingam on July 12, 2006, 01:11:07 pm
And will the support for the Digital Mars D compiler be improved any time soon?
Title: Re: The 11 July 2006 build is out.
Post by: C D Tamhankar on July 12, 2006, 06:23:19 pm
Any plans of incorporating GCC 4.1.1 as a default compiler for 1.0-RC3 version ?

GCC 4.x hasn't been released for windows. How could we distribute it?  :shock:

GCC 4.1.1 - MinGW.7z     27-May-2006 23:51
This is a binary snapshot of GCC 4.1.1.    Ref:  http://gda.utp.edu.co/~ceniza/GCC-4.1.1/

Sorry! I misunderstood it as a offical release

Title: Re: The 11 July 2006 build is out.
Post by: mandrav on July 12, 2006, 07:03:40 pm
Ceniza is kind enough to provide a gcc-4.1 snapshot, but it's not official in any way...
Title: Re: The 11 July 2006 build is out.
Post by: TheNullinator on July 12, 2006, 07:42:47 pm
About the toolbar-images-not-changing-state issue: I've noticed on my laptop (WinXP SP2) that the debugger stop toolbar icon is greyed out when the debugger is not running but now the "Debug" menu stop icon doesn't grey out.  The menu icon used to work properly.  So they have swapped for me at least.

Has anyone else noticed this?  Maybe this was mentioned in the past but I couldn't find anything searching.