Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on June 19, 2007, 07:38:56 pm

Title: The 19 June 2007 build is out.
Post by: killerbot on June 19, 2007, 07:38:56 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/wxmsw28u_gcc_cb_wx284.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

The 19 June 2007 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20070619_rev4107_win32.7z
  - Linux :
   http://prdownload.berlios.de/codeblocks/CB_20070619_rev4107_Ubuntu6.10+7.04_wx2.8.4.deb
   http://prdownload.berlios.de/codeblocks/CB_20070619_rev4107_suse100-102.wx28.i586.rpm (not yet)
   http://prdownload.berlios.de/codeblocks/CB_20070619_rev4107_fc4+5.i586.rpm (not yet)


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 19 June 2007 build is out.
Post by: Biplab on June 19, 2007, 07:50:39 pm
Windows Nightly revision number is incorrect.
Title: Re: The 19 June 2007 build is out.
Post by: lubos on June 19, 2007, 07:52:14 pm
yep
http://prdownload.berlios.de/codeblocks/CB_20070619_rev4107_win32.7z (http://prdownload.berlios.de/codeblocks/CB_20070619_rev4107_win32.7z)
Title: Re: The 19 June 2007 build is out.
Post by: cstudent on June 19, 2007, 10:18:50 pm
Debian package:

http://www.mediafire.com/?4xcmtmbpnxg
Title: There is a bug in build log saving module.
Post by: luoyonggang on June 20, 2007, 08:32:00 am
The log file is not specify the encode standard,so it's will post incorrect things when i explore it in the Internet Explorer. I was using simplified Chinese Operating system, and in there is some simplified Chinese Characters in the log. So i think in the log file you must specify the chartset so that the browser can recognize the log file in a correct way.
Build log saved as: unnamed_build_log.html
Title: Re: The 19 June 2007 build is out.
Post by: skirby on June 20, 2007, 12:44:33 pm
Hello,

I have found a bug in this release (I haven't done the test with previous release).
- Create a simple Dos project with accented character in you project path like D:\Mélange
- Make an error somewhere in the code.
- Compile the project => In Build message window, you can see the error

Nothing happened if you double click on Build message window.
Normally, C::B goes on the line in error.
It does not happen if path does not contains accented character.

You can see a screenshot here:
(http://img80.imageshack.us/img80/1464/bugvm1.th.png) (http://img80.imageshack.us/my.php?image=bugvm1.png)

I hope you could fix it.

Thanks and have a nice day.
Title: Re: The 19 June 2007 build is out.
Post by: David Perfors on June 20, 2007, 01:24:26 pm
Could you show the output of the Build log?
Title: Re: The 19 June 2007 build is out.
Post by: skirby on June 20, 2007, 01:55:27 pm
Sure I can !
(http://img522.imageshack.us/img522/3154/bug2ue9.th.png) (http://img522.imageshack.us/my.php?image=bug2ue9.png)
Title: Re: The 19 June 2007 build is out.
Post by: MortenMacFly on June 20, 2007, 02:04:16 pm
I hope you could fix it.
I am currently testing a patch that should tackle this.
If you want to, try replacing line 40 in compiler.cpp which is currently:
Code
const wxString Compiler::FilePathWithSpaces = _T("[][{}() \t#%$~A-Za-z0-9_:+/\\.-]+");
...with:
Code
#ifdef __WXMSW__
const wxString Compiler::FilePathWithSpaces = _T("[a-zA-Z]:\\[^/:*?\"<>]*\\?[^\\/:*?\"<>]*");
#else
const wxString Compiler::FilePathWithSpaces = _T("[.]{0,2}[/][^/:*?\"<>]*/?[^//:*?\"<>]*");
#endif                                           
That's also the root of the culprit btw... ;-)
With regards, Morten.

Edit: Ok... that's not supposed to work... forget about it for a while...
Title: Re: The 19 June 2007 build is out.
Post by: killerbot on June 20, 2007, 02:41:39 pm
note that thos special symbols need to be there :

Eg. : C:\My{direc tor]y\I[s he(re)

is a valid dir : how stupid it may be, but it is
Title: Re: The 19 June 2007 build is out.
Post by: MortenMacFly on June 20, 2007, 02:57:48 pm
Eg. : C:\My{direc tor]y\I[s he(re)
is a valid dir : how stupid it may be, but it is
I know. That's why I'm trying to do it the opposite way: *forbid* certain characters (notice the ^ in the RegExp) but allow all others.
With regards, Morten.

Edit: Now this should actually work:
Code
#ifdef __WXMSW__
const wxString Compiler::FilePathWithSpaces = _T("[a-zA-Z]:\\\\[^/:*?\\\"<>]*\\\\?|[^/:*?\\\"<>]*");
#else
const wxString Compiler::FilePathWithSpaces = _T("[.]{0,2}[/][^\\\\:*?\\\"<>]*/?|[^\\\\:*?\\\"<>]*");
#endif                                           
Title: Re: The 19 June 2007 build is out.
Post by: skirby on June 20, 2007, 03:21:06 pm
Why don't you simply exclude only these characters:
Quote
\ / : * ? " < > |

Windows forbid these characters when you create or rename a folder.
Title: Re: The 19 June 2007 build is out.
Post by: David Perfors on June 20, 2007, 03:27:03 pm
Morton, just a reminder ;)
could you use the simple C++ statement:
Code
if(platform::windows)
(see prep.h and the anti macro's topics on the forums ;))
Title: Re: The 19 June 2007 build is out.
Post by: MortenMacFly on June 20, 2007, 03:29:52 pm
Code
if(platform::windows)
(see prep.h and the anti macro's topics on the forums ;))
I can't, as this is a const global variable... ;-)
Title: Re: The 19 June 2007 build is out.
Post by: MortenMacFly on June 20, 2007, 03:31:24 pm
Why don't you simply exclude only these characters:
Quote
\ / : * ? " < > |
Windows forbid these characters when you create or rename a folder.
Keep in mind we are cross-platform. But for windows this is what I'm actually trying to do, including to verify a correct file syntax (with drive letter etc...)
With regards, Morten.

Edit: BTW: It really seems to work now, the "Mélange" example at least...
Could some other devs have a look at this proposal, too, please?!
Title: Re: The 19 June 2007 build is out.
Post by: thomas on June 20, 2007, 05:08:40 pm
I can't, as this is a const global variable... ;-)
Works fine with ternary operator, but I don't think it really matters in this case.


On a different note, why don't you use a much simpler regex?
The compiler outputs a filename, and a colon followed by a digit (= line number), and/or a colon followed by a space character.
Everything after the second colon is the message. Everything before that colon is the pathname. So... match for a colon followed by a digit, and a colon followed by a space.
Something like : ({0-9}+:)?\s, with some additional ()s added to grab the filename, line number, and text.

EDIT: there is an additional space in the above regex that doesn't belong there, but the super-smart  forum software would otherwise insert a :(

We don't know what a pathname looks like, or whether it's French or Chinese, whether it's an Unix filename, DOS, or whatever. And we don't really care. Whatever it is, it ends with a colon followed by a digit followed by a colon and a space, or a colon followed by a space character.

You just have to pay attention not to match a colon inside D:\, but since neither a digit, nor a space is legal in that place, this should be no issue.
Title: Re: The 19 June 2007 build is out.
Post by: MortenMacFly on June 20, 2007, 08:25:23 pm
I can't, as this is a const global variable... ;-)
Works fine with ternary operator, but I don't think it really matters in this case.
Oh - really?! I should try that. Thats nice! :-)

On a different note, why don't you use a much simpler regex?
How simple shall that be? What I'm trying to do is to exclude characters that are not allowed by the OS files system. There is even a wx method that returns such a list of characters platform depended (I'm currently playing around with that). I think a solution that includes possible characters will fail in cases we don't think of atm. (I interpret your proposal as such or how did you mean that...?!). The RegEx is so long for the simple reason that there *might* be a "[DriveLetter]:\" in front and only there (the old RegEx allowed colons anywhere in the path).

So... match for a colon followed by a digit, and a colon followed by a space.
This I don't get at all: Why "colon followed by a space"? We are parsing a filename in a (error/warning) message where there can only be one colon after the drive letter followed by a backslash (on Windows only, of course). Maybe you can explain that in more detail?! I guess I'm still missing something obvious here...

With regards, Morten.
Title: Re: The 19 June 2007 build is out.
Post by: bosca on June 20, 2007, 08:58:28 pm
Hello the guys!
Bravo for codeblocks, in time it matures as a good wine of Anjou. :oops:
I am under Debian Etch and I have an error in the compilation, what gives this: :shock:
Code
g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread -I../../../src/include -I../../../src/include/wxscintilla/include -I../../../src/include/scripting/include -I../../../src/include/scripting/sqplus -Ulinux -Uunix -O2 -ffast-math -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT gdb_driver.lo -MD -MP -MF .deps/gdb_driver.Tpo -c gdb_driver.cpp  -fPIC -DPIC -o .libs/gdb_driver.o
if /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread  -I../../../src/include -I../../../src/include/wxscintilla/include -I../../../src/include/scripting/include -I../../../src/include/scripting/sqplus  -Ulinux -Uunix  -O2 -ffast-math -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT gdb_tipwindow.lo -MD -MP -MF ".deps/gdb_tipwindow.Tpo" -c -o gdb_tipwindow.lo gdb_tipwindow.cpp; \
        then mv -f ".deps/gdb_tipwindow.Tpo" ".deps/gdb_tipwindow.Plo"; else rm -f ".deps/gdb_tipwindow.Tpo"; exit 1; fi
 g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread -I../../../src/include -I../../../src/include/wxscintilla/include -I../../../src/include/scripting/include -I../../../src/include/scripting/sqplus -Ulinux -Uunix -O2 -ffast-math -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT gdb_tipwindow.lo -MD -MP -MF .deps/gdb_tipwindow.Tpo -c gdb_tipwindow.cpp  -fPIC -DPIC -o .libs/gdb_tipwindow.o
gdb_tipwindow.cpp:40:25: error: gtk/gtk.h: No such file or directory
gdb_tipwindow.cpp: In constructor 'GDBTipWindow::GDBTipWindow(wxWindow*, const wxString&, const wxString&, const wxString&, const wxString&, wxCoord, GDBTipWindow**, wxRect*)':
gdb_tipwindow.cpp:190: error: 'GTK_WIDGET_HAS_GRAB' was not declared in this scope
gdb_tipwindow.cpp:191: error: 'gtk_grab_add' was not declared in this scope
gdb_tipwindow.cpp: In destructor 'virtual GDBTipWindow::~GDBTipWindow()':
gdb_tipwindow.cpp:207: error: 'GTK_WIDGET_HAS_GRAB' was not declared in this scope
gdb_tipwindow.cpp:208: error: 'gtk_grab_remove' was not declared in this scope
gdb_tipwindow.cpp: In member function 'void GDBTipWindow::Close()':
gdb_tipwindow.cpp:261: error: 'GTK_WIDGET_HAS_GRAB' was not declared in this scope
gdb_tipwindow.cpp:262: error: 'gtk_grab_remove' was not declared in this scope
make[4]: *** [gdb_tipwindow.lo] Erreur 1
make[4]: quittant le répertoire « /home/stephane/trunk/src/plugins/debuggergdb »
make[3]: *** [all-recursive] Erreur 1
make[3]: quittant le répertoire « /home/stephane/trunk/src/plugins/debuggergdb »
make[2]: *** [all-recursive] Erreur 1
make[2]: quittant le répertoire « /home/stephane/trunk/src/plugins »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/stephane/trunk/src »
make: *** [all-recursive] Erreur 1
stephane@robusta:~/trunk$ cd
 
T7200 2gb RAM HD160gb :lol:
rev 4107 and 4122/4123
wxwidgets2.8.4
./bootstrap;./configure --enable-contrib;make;su -c 'make install'

Still thank you for your fantastic work! :P
Cordially Stéphane
Title: Re: The 19 June 2007 build is out.
Post by: mandrav on June 20, 2007, 09:50:12 pm
Hello the guys!
Bravo for codeblocks, in time it matures as a good wine of Anjou. :oops:
I am under Debian Etch and I have an error in the compilation, what gives this: :shock:
Code
...
...
...
T7200 2gb RAM HD160gb :lol:
rev 4107 and 4122/4123
wxwidgets2.8.4
./bootstrap;./configure --enable-contrib;make;su -c 'make install'

Still thank you for your fantastic work! :P
Cordially Stéphane

You need pkg-config and gtk+ devel packages.
Title: Re: The 19 June 2007 build is out.
Post by: pauliusz on July 03, 2007, 10:49:45 pm
How is it going Morten?

I have some issues with this also...