Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on January 19, 2007, 08:28:14 pm

Title: The 19 January 2007 build is out.
Post by: killerbot on January 19, 2007, 08:28:14 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

To fix the menu alignment bug introduced in wx 2.6.3 [windows only bug] we have patched wx ourselves, and that results in the following alternative dll : http://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2AndCbPatch_version3.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 19 January 2007 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20070119_rev3507_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20070119_rev3507_Ubuntu6.xx.deb
         http://prdownload.berlios.de/codeblocks/CB_20070119_rev3507_suse100+101.i586.rpm
         http://prdownload.berlios.de/codeblocks/CB_20070119_rev3507_fc4+5.i586.rpm


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 19 January 2007 build is out.
Post by: jiao on January 19, 2007, 10:25:30 pm
Nice job thanks!

I was wondering, is there any way to pull the nightly builds from SVN instead of having to download the package and unzip it everytime?
Title: Re: The 19 January 2007 build is out.
Post by: killerbot on January 19, 2007, 10:36:40 pm
nope, svn == sources, but buildin cb with cb is fun ;-)
Title: Re: The 19 January 2007 build is out.
Post by: nenin on January 19, 2007, 10:56:41 pm
Debugger not working:
Corrected  :? Project lost -g in debug branch  :shock:
Title: Re: The 19 January 2007 build is out.
Post by: killerbot on January 19, 2007, 11:01:08 pm
with todays nightly ?
Title: Re: The 19 January 2007 build is out.
Post by: nenin on January 19, 2007, 11:05:12 pm
Quote from: killerbot on January 19, 2007, 11:01:08 pm
with todays nightly ?
I have some odd troubles with this project in older builds. Probably, somewhere I lost "-g".
Now it looks OK.
Title: Re: The 19 January 2007 build is out.
Post by: Belgabor on January 20, 2007, 03:57:40 am
I just wanted to confirm the problem with compiling rc files for this nightly reported in the 18.1. thread, although it seems pretty strange:
Code
windres.exe -i "F:\Development\svn\RCT3 Importer\src\RCT3 Tool\wxapp.rc" -J rc -o "..\..\lib\obj\release dll\wxapp.res" -O coff -IF:\MinGW\include -IF:\MinGW\include\wx-2.8 
gcc: F:\Development\svn\RCT3: No such file or directory
gcc: Importer\src\RCT3: No such file or directory
gcc: Tool\wxapp.rc: No such file or directory
gcc: warning: '-x c' after last input file has no effect
gcc: no input files
windres.exe: no resources
Process terminated with status 1 (0 minutes, 0 seconds)
1 errors, 1 warnings
Title: Re: The 19 January 2007 build is out.
Post by: basurapr on January 20, 2007, 05:16:34 am
Stick with the 10th january revision,

I think theres a problem with white spaces introduced

---------------------------------------------------------------------------
Compiling: resource.rc
gcc: Files\codeblocks\SDK\wxWidgets-2.8.0\include: No such file or directory
gcc: F:\Mis: No such file or directory
gcc: Documentos\C: No such file or directory
gcc: Projects\MyProject\resource.rc: No such file or directory
gcc: warning: `-x c' after last input file has no effect
gcc: no input files
windres.exe: no resources
---------------------------------------------------------------------------

=============================================
diretories should be:

second line is
C:\Program Files\codeblocks\SDK\wxWidgets-2.8.0\include

The third, fourth and fifth lines:
F:\Mis Documentos\C Projects\MyProject\resource.rc
=============================================

the commands are stripped by the spaces, i think that the file arguments are not sended with \" characters(").
Title: Re: The 19 January 2007 build is out.
Post by: Poobah on January 20, 2007, 10:44:32 am
I don't think that Windres (the GNU RC script compiler) even supports file names with spaces. Code::Blocks should just rename them before and after compiling when GCC is selected as the compiler.
Title: Re: The 19 January 2007 build is out.
Post by: Marenz on January 20, 2007, 11:12:30 am
I noticed that cb doesn't save the changed files when i compile them. This is on rev 3515, debian etch amd64. I use a custom makefile.

--Ano
Title: Re: The 19 January 2007 build is out.
Post by: cbexaminr on January 20, 2007, 12:03:26 pm
thought regarding spaces - could the problem have always been there, but the switch to full paths that include them has caused it to be revealed...

whereas the previous relative paths perhaps contained no (path/directory) segments that had spaces in them (such as "Program Files", or "C Development")?

Should all absolute paths (at least with spaces) be quoted in the command lines?
Title: Re: The 19 January 2007 build is out.
Post by: basurapr on January 20, 2007, 02:45:22 pm
Quote from: cbexaminr on January 20, 2007, 12:03:26 pm
Should all absolute paths (at least with spaces) be quoted in the command lines?

Yes, I think that the arguments should be sended quoted to the compiler. When the argument have spaces like this: C:\Program Files, it will pass like two arguments, "C:\Program" and "Files" to the char** argv array. It should be "C:\Program Files" to stop the problem. Maybe I'm wrong!  :?
Title: Re: The 19 January 2007 build is out.
Post by: julienlecomte on January 20, 2007, 05:56:14 pm

FYI:
There's some SDK mismatch problem with the ClearCase plugin with this build. To avoid error message at startup, I just deleted the clearcase zip and dll.
Title: Re: The 19 January 2007 build is out.
Post by: killerbot on January 20, 2007, 05:57:48 pm
Quote from: julienlecomte on January 20, 2007, 05:56:14 pm

FYI:
There's some SDK mismatch problem with the ClearCase plugin with this build. To avoid error message at startup, I just deleted the clearcase zip and dll.


yes, destroy it, this is a personal plug-in that sneaked into the nightly zip, my mistake. Off course I you use clearcase I can always provide you with a newer one ;-)
Title: Re: The 19 January 2007 build is out.
Post by: branleb on January 20, 2007, 07:27:52 pm
I  have openSuSE 10.2 and i installed C::B rpm for suse10.0/10.1 (nigthly)
The splash screen appearing at the start always shows BUILD# "SVN 0", could anyone confirm ?
and is so, could you fix it ?
it is not so important, but it doesn't look so good with version number "0" ;-)
Title: Re: The 19 January 2007 build is out.
Post by: Acki on January 20, 2007, 09:09:48 pm
Hi,
when I click on an error message in the "Build messages" tab it doesn't jump to the error line in the editor now !?!?!
Anyone else has this problem, too ???
Title: Re: The 19 January 2007 build is out.
Post by: Pecan on January 20, 2007, 09:31:02 pm
Quote from: Acki on January 20, 2007, 09:09:48 pm
Hi,
when I click on an error message in the "Build messages" tab it doesn't jump to the error line in the editor now !?!?!
Anyone else has this problem, too ???


This takes a double left click now.
Title: Re: The 19 January 2007 build is out.
Post by: indigo0086 on January 21, 2007, 12:59:00 am
I was wondering is there a way to set the default directories for build/release and stuff.  Also I was wondering when I import a solution or project from visual studio if it can automatically port those default directories.  I've noticed that some solutions and visual studio projects have their own directories that C::B doesn't create.
Title: Re: The 19 January 2007 build is out.
Post by: Acki on January 21, 2007, 01:31:01 am
Quote from: Pecan on January 20, 2007, 09:31:02 pm
This takes a double left click now.

That's what I mean...  :roll:
It doesn't work !!!
Title: Re: The 19 January 2007 build is out.
Post by: Kazade on January 21, 2007, 01:32:16 am
I dunno if it is just this revision, or because this is the first time i've used C::B solidly for hours but copy and paste doesnt work properly. I can copy and paste something, and it doesnt always copy, so the paste sometimes pastes the copy before the copy... if that makes any sense. Its the same with Cut. I'm using the Ubuntu version, is anyone else having this trouble? For a while I thought I was just going mad and not pressing the copy keys, but because the same thing happens with Cut I know its not my imagination. I searched the forums and came across this: http://forums.codeblocks.org/index.php?topic=2929.0 from April. Its exactly the same problem im having.
Title: Re: The 19 January 2007 build is out.
Post by: Pecan on January 21, 2007, 01:43:48 am
Quote from: Acki on January 21, 2007, 01:31:01 am
Quote from: Pecan on January 20, 2007, 09:31:02 pm
This takes a double left click now.

That's what I mean...  :roll:
It doesn't work !!!

I just double clicked on the error below, and the cursor jump to the erroneous line.

(http://img411.imageshack.us/img411/4868/1157wj.png)
Title: Re: The 19 January 2007 build is out.
Post by: Belgabor on January 21, 2007, 06:51:35 pm
Quote from: cbexaminr on January 20, 2007, 12:03:26 pm
thought regarding spaces - could the problem have always been there, but the switch to full paths that include them has caused it to be revealed...

I also thought about this possibility, and for my project that could well be the case.
Title: Re: The 19 January 2007 build is out.
Post by: Acki on January 21, 2007, 08:12:13 pm
Quote from: Pecan on January 21, 2007, 01:43:48 am
I just double clicked on the error below, and the cursor jump to the erroneous line.

I tried everything, it doesn't work for me !!!
I also reinstalled my complete system (W2k-sp4) !!!
Title: Re: The 19 January 2007 build is out.
Post by: killerbot on January 21, 2007, 08:59:35 pm
can you try with an older nightly build, eg from last december ? this is very weird ...
Title: Re: The 19 January 2007 build is out.
Post by: mandrav on January 21, 2007, 09:57:15 pm
Quote from: Acki on January 21, 2007, 08:12:13 pm
Quote from: Pecan on January 21, 2007, 01:43:48 am
I just double clicked on the error below, and the cursor jump to the erroneous line.

I tried everything, it doesn't work for me !!!
I also reinstalled my complete system (W2k-sp4) !!!


Acki,

first things first: try NOT ending all your sentences with exclamation marks !!!

Second, give us some info please and stop generalizing. Saying "it doesn't work" isn't giving us enough (if any!) clues on what might be wrong so that we can help you. For example, give us the directory structure of your project: how it is laid out and what filename is on the build-messages line you 're double-clicking and isn't taking you where it should...

In other words: help us help you :).
Title: Re: The 19 January 2007 build is out - Slackware 11 package
Post by: jsibarani on January 23, 2007, 11:49:40 am
Hi,
I've uploaded codeblocks revision 3507 for Slackware 11 .

you can download codeblocks and wxWidgets-2.6.3  .tgz
here. (http://www.savefile.com/projects/1071125)


Thanks
Title: Re: The 19 January 2007 build is out.
Post by: Belgabor on January 23, 2007, 10:16:47 pm
Quote from: Belgabor on January 21, 2007, 06:51:35 pm
Quote from: cbexaminr on January 20, 2007, 12:03:26 pm
thought regarding spaces - could the problem have always been there, but the switch to full paths that include them has caused it to be revealed...

I also thought about this possibility, and for my project that could well be the case.

Actually I was partly wrong. My output directory has (and always had) a space, so only the input dir seems to be affected.
Title: Re: The 19 January 2007 build is out.
Post by: line on January 29, 2007, 01:39:20 am
I'm using the windows version of the nightly builds for coding D console apps with the GDC compiler.
Since installing this version of CodeBlocks, I am unable to execute any D programs from the IDE. They build correctly, but when I press F9, nothing happens. No output, nothing at all.
C/C++ projects seem to be unaffected, and the lack of an actual error message makes it kind-of hard to figure this one out. But it's definitely a problem that has been introduced in this build - it works with the previous one.
If I switch the type from command-line application to GUI application, it also works.
Any ideas?

Update: WHAT THE HELL. After switching to GUI application and back, I find myself unable to reproduce the error. I am sorry for the false alarm.