Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on February 14, 2007, 08:33:24 pm

Title: The 14 february 2007 build is out.
Post by: killerbot on February 14, 2007, 08:33:24 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 14 February 2007 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20070214_rev3607_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20070214_rev3607_Ubuntu6.xx.deb
         http://prdownload.berlios.de/codeblocks/CB_20070214_rev3607_suse100-102.i586.rpm
         http://prdownload.berlios.de/codeblocks/CB_20070214_rev3607_fc4+5.i586.rpm


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 14, 2007, 08:42:11 pm
since the directory movings it seems that there's no svn revision in the exe (about, start here or splash screen) , no idea why yet ...
Title: Re: The 14 february 2007 build is out.
Post by: sethjackson on February 14, 2007, 08:48:09 pm
Windows ANSI build here (http://savefile.com/files/491748).
Title: Re: The 14 february 2007 build is out.
Post by: PsYhLo on February 14, 2007, 09:21:26 pm
Why SVN doesn't work :(
i can't get the latest svn revision

it gives me this when i start to update my local rev with
Code
svn up
from my console
Code
svn: Can't connect to host 'svn.berlios.de': ÷·ðï¿(8ø·

OS: Ubuntu 6.10
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 14, 2007, 09:49:12 pm
since the directory movings it seems that there's no svn revision in the exe (about, start here or splash screen) , no idea why yet ...

Did you delete or rename the SDK folder and update it using SVN to recreate it, I had a lot of weird issues till I did that at first under windows.

Tim S

Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 14, 2007, 10:02:37 pm
Why SVN doesn't work :(
i can't get the latest svn revision

it gives me this when i start to update my local rev with
Code
svn up
from my console
Code
svn: Can't connect to host 'svn.berlios.de': ÷·ðï¿(8ø·

OS: Ubuntu 6.10

Works for me, what protocol are you using? http or svn? I believe that I am using svn:

Tim S
Title: Re: The 14 february 2007 build is out.
Post by: MortenMacFly on February 14, 2007, 10:05:43 pm
Did you delete or rename the SDK folder and update it using SVN to recreate it, [...]
That's in fact a good way to do (and highly recommended). Maybe it's best to do a fresh SVN checkout if somebody experiences compiler issues. It's not only the new directory structure that has changed but also the project's setup (e.g. place of object, lib and pch files). It's not easy to clean the sandbox without good "inside-knowledge". ;-)
With regards, Morten.
Title: Re: The 14 february 2007 build is out.
Post by: indigo0086 on February 15, 2007, 03:19:54 am
I never asked cuz I thought I'd look dumb, but what is the difference between the regular windows build and the ANSI one?
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 15, 2007, 03:44:43 am
I never asked cuz I thought I'd look dumb, but what is the difference between the regular windows build and the ANSI one?

ANSI means NON Unicode in this case, Unicode is a method to handle Languages that require more than 256 codes to handle the language (Also allows you to mix multiple Languages together). ANSI standards defines the way to represent many different Languages(only one Language at a time) modified from ASCII using 256 code values (8 bits per character). This is a very simple definition that may not be perfect but I hope gets the idea across. 

Links That may help to understand
http://en.wikipedia.org/wiki/Unicode
http://en.wikipedia.org/wiki/ISO_8859
http://en.wikipedia.org/wiki/Code_page#Windows_.28ANSI.29_code_pages


Tim S
Title: Re: The 14 february 2007 build is out.
Post by: dronT78 on February 15, 2007, 12:40:27 pm
Quote
wxWidgets Wizard: Added support for wxWidgets 2.9.x (CVS Branch)
Wow! I'm use wx 2.9 from yesterday. Thanks!
Title: Re: The 14 february 2007 build is out.
Post by: TheTuxKeeper on February 15, 2007, 12:42:04 pm
I found a strange behavior. I loaded the cb's unix project and opened a random file.
When I want to use the combobox, where you can jump between the function definitions, the dropdown menu disappears when I move the mouse. Sometimes it needs several tries till I can select one item and sometimes I can move the mouse but when I click the menu disappears and nothing happens  :shock:

Can someone confirm this ?

I use rev3607 on suse 10.2.

btw. the build target selection works, if I clear history, restart and open the project. But if I restart with the project in history the build target combobox disappears as already reported.
Title: Re: The 14 february 2007 build is out.
Post by: Joerg on February 15, 2007, 01:51:29 pm
Why does C::B need the mingw.dll,
even if I don't use mingw for compiling?
Greets
Title: Re: The 14 february 2007 build is out.
Post by: Pecan on February 15, 2007, 02:12:20 pm
I found a strange behavior. I loaded the cb's unix project and opened a random file.
When I want to use the combobox, where you can jump between the function definitions, the dropdown menu disappears when I move the mouse. Sometimes it needs several tries till I can select one item and sometimes I can move the mouse but when I click the menu disappears and nothing happens  :shock:

Can someone confirm this ?

I use rev3607 on suse 10.2.

btw. the build target selection works, if I clear history, restart and open the project. But if I restart with the project in history the build target combobox disappears as already reported.

Yes, but I get it on svn 3590 when using the debugger.
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 15, 2007, 02:46:43 pm
Why does C::B need the mingw.dll,
even if I don't use mingw for compiling?
Greets

It does NOT need the mingw.dll, except for on windows where since minGW was used to compile and build Code::Blocks it needs it to run.

Tim S
Title: Re: The 14 february 2007 build is out.
Post by: manianis on February 15, 2007, 02:47:37 pm
It says SVN 0
Title: Re: The 14 february 2007 build is out.
Post by: Biplab on February 15, 2007, 03:22:17 pm
@Killerbot,

I did face that SVN problem (SVN Number is showing as 0). I've solved it by adding PATH variable pointing svn bin directory in C::B environment. :)
Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 15, 2007, 08:15:01 pm
do you mean, adding the path of the svn exe to system PATH ??
I use tortoise svn, and I prefer to keep my path as clean as possible.
It used to work before the code restructuring, so it should be possible to have it workin again. Unfortunately i don't have time to sort it out at the moment, so all help is welcome.
Title: Re: The 14 february 2007 build is out.
Post by: PsYhLo on February 15, 2007, 09:12:51 pm

Works for me, what protocol are you using? http or svn? I believe that I am using svn:

Tim S


svn://svn.berlios.de/codeblocks/trunk
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 15, 2007, 09:20:10 pm
do you mean, adding the path of the svn exe to system PATH ??
I use tortoise svn, and I prefer to keep my path as clean as possible.
It used to work before the code restructuring, so it should be possible to have it workin again. Unfortunately i don't have time to sort it out at the moment, so all help is welcome.

Any other svn tools on your machine?

Note, I read somewhere on this board that they just started using the svn tool using xml output. I think I might be able to find a way to have it work without have it needed to be added to the system path, but I think you will need an SVN tool that does XML output. No, Idea if tortoise svn does I will see if it does I have it on my machine.

Tim S
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 15, 2007, 10:25:56 pm

Works for me, what protocol are you using? http or svn? I believe that I am using svn:

Tim S


svn://svn.berlios.de/codeblocks/trunk

Is it still not working?
If not, have you tried pinging or trace routes to verify connectivity issues?

Tim S
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 16, 2007, 01:08:27 am
do you mean, adding the path of the svn exe to system PATH ??
I use tortoise svn, and I prefer to keep my path as clean as possible.
It used to work before the code restructuring, so it should be possible to have it workin again. Unfortunately i don't have time to sort it out at the moment, so all help is welcome.

Any other svn tools on your machine?

Note, I read somewhere on this board that they just started using the svn tool using xml output. I think I might be able to find a way to have it work without have it needed to be added to the system path, but I think you will need an SVN tool that does XML output. No, Idea if tortoise svn does I will see if it does I have it on my machine.

Tim S

If you have svn.exe on your PC, you can add "C:\Program Files\Subversion\bin" to the compiler "Tool chain Excutable" "Additional Path". I just tested it and it works for me. Note, the "bin" sub-folder was required.

Note, my svn.exe was version 1.4.2.22196.

Tim S
Title: Re: The 14 february 2007 build is out.
Post by: Biplab on February 16, 2007, 02:21:01 am
do you mean, adding the path of the svn exe to system PATH ??
I use tortoise svn, and I prefer to keep my path as clean as possible.
It used to work before the code restructuring, so it should be possible to have it workin again. Unfortunately i don't have time to sort it out at the moment, so all help is welcome.

@killerbot, sorry my reply was not bit clear.

I do use TortoiseSVN. But the problem with TortoiseSVN is there is no svn.exe file in the installation folder. So autorevision.exe will fail to create a proper autorevision.h file.

What I did-

Basically that solved my problem.

But you'll notice another problem. You'll see that in Start page, the time is bit peculiar. I've reported this problem along with a patch to solve it in the following thread.

http://forums.codeblocks.org/index.php?topic=5179.msg40569#msg40569

Hope this solves your problem. :D

Regards,

Biplab
Title: Re: The 14 february 2007 build is out.
Post by: LCsquare on February 16, 2007, 07:49:03 am
Also the code parsing (I mean the symbol table in Management Dialog) is a bit crashed. (from 8/2/2007 nightly build)

During I switch focus files, the "Current file symbols" will sometimes display nothing.

I need to re-activate the corresponding project, then switch the "View" to "Active Project Symbols", then back to "Current file symbols" in order to restore the expected symbols table.

Please help.
Title: Re: The 14 february 2007 build is out.
Post by: Kalma on February 16, 2007, 01:52:47 pm
Hello,
I have found a nother way to solve this problem with svn.exe.
My Idea was to ad a little .bat file named svn.bat which is called by autorevision.exe.
It consists of:
Code
C:\Programme\svn-win32-1.4.3\bin\svn.exe %*
.
Before the dir restructoring it worked fine for me but now there is also only "Revision 0" on the
Splashscreen and so on.
Title: Re: The 14 february 2007 build is out.
Post by: stahta01 on February 16, 2007, 01:58:31 pm
Hello,
I have found a nother way to solve this problem with svn.exe.
My Idea was to ad a little .bat file named svn.bat which is called by autorevision.exe.
It consists of:
Code
C:\Programme\svn-win32-1.4.3\bin\svn.exe %*
.
Before the dir restructoring it worked fine for me but now there is also only "Revision 0" on the
Splashscreen and so on.

Where did you put the svn.bat file?

Tim S
Title: Re: The 14 february 2007 build is out.
Post by: Kalma on February 16, 2007, 02:09:51 pm
@stahta01

I have put it in the autorevision Folder. Where the autorevision.exe is build.
Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 16, 2007, 04:44:16 pm
When one has TortoiseSvn installed, there's no svn.exe. So bit ackward to add yet another svn client. So will revert temporarily back to previous method and wait till Thomas i back to fully fix the issue. It has worked in the past without pah adjusting and without extra svn installs, so probably should keep working like this ...
Title: Re: The 14 february 2007 build is out.
Post by: Biplab on February 16, 2007, 05:02:48 pm
@killerbot,

You are right, earlier it used to work without svn.exe.

I've mentioned another problem. Did you face that? I'm bit confused with that. In Windows build I'm getting that problem, but in Linux that problem is not coming up. Don't know why? (Windows & Linux build based on Revision 3609, Windows with my patch, Linux without any patch) :!:
Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 16, 2007, 05:19:00 pm
I also have it in linux : "svn build rev 3609 (2007-02-15T15:43:11.509615Z) gcc 4.1.2 Linux/unicode"

Well more work for Thomas ;-)
Title: Re: The 14 february 2007 build is out.
Post by: Biplab on February 16, 2007, 05:23:01 pm
I also have it in linux : "svn build rev 3609 (2007-02-15T15:43:11.509615Z) gcc 4.1.2 Linux/unicode"

Well more work for Thomas ;-)

Thanks for the reply. :D

Try applying my patch. It basically removes unwanted characters. But it doesn't fix any time zone related conversions. I hope there's not much work for Thomas.  ;)
Title: Re: The 14 february 2007 build is out.
Post by: gjsmo on February 17, 2007, 02:07:39 am
I have a problem with this build. The tabs are broken. If you open enough tabs so that they cannot all fit, the arrow buttons become enabled. However, if you close enough tabs so that they can all fit, the buttons stay enabled because the tabs are not all put up on the "tab bar" - they are scrolled over even though they could go over. This happens all the time, and I would think it be easily reproducible. I am not sure what the bug is in, as I am not familiar with the C::B code, but I would think it has something to do with wxWidgets.
Title: Re: The 14 february 2007 build is out.
Post by: Alturin on February 18, 2007, 12:59:18 am
Not sure if I understood it right, but did you try hitting the "<" arrow button? I have the same "problem" and it's solved by hitting it till all the tabs fill the bar. But it is a bit strange that that isn't done automagically.
Title: Re: The 14 february 2007 build is out.
Post by: steveth45 on February 19, 2007, 10:32:31 pm
I'm running openSUSE 10.2.  This version of C::B loaded up fine a few times, but now it claims that the program is already running when I try to start up.  I can see no evidence of codeblocks running anywhere (top).  I even wiped the ~/.codeblocks folder, and it still thinks its already running.  I can't get it running to change the setting to allow multiple instances to run.  However, this is not the problem, since there is no "codeblocks" process running at all, even though it thinks there is.
Title: Re: The 14 february 2007 build is out.
Post by: thomas on February 20, 2007, 09:56:40 am
When one has TortoiseSvn installed, there's no svn.exe. So bit ackward to add yet another svn client. So will revert temporarily back to previous method and wait till Thomas i back to fully fix the issue. It has worked in the past without pah adjusting and without extra svn installs, so probably should keep working like this ...
Ho ho, and back he is... hello again :)

It really cannot have worked without. If it did work, you had a Subversion executable and in your PATH and you did not know :)
Autorevision has always been and is still only calling svn.exe, so if that file does not exist or cannot be found (it obviously either has to be in PATH or in the same directory), it won't work, and it never worked.
It may be possible to call Tortoise as a backup solution if installed... in the past, this was awkward, but possible... not sure we should, though. Tortoise is not very much cross platform :)

I also have it in linux : "svn build rev 3609 (2007-02-15T15:43:11.509615Z) gcc 4.1.2 Linux/unicode"
Well more work for Thomas ;-)
Try applying my patch. It basically removes unwanted characters. But it doesn't fix any time zone related conversions. I hope there's not much work for Thomas.  ;)
Yep, I'm aware of this issue. However, the point in switching to xml output was that I did *not* want to parse strings manually and figure out something that might be a date any more (which will always go wrong in some cases). Even though the timestamp output by Subversion currently seems to be (always?) ISO-formatted, we don't really know. It may be on some platforms, not on others, and it may change in the next revision (they made more drastic changes in the past).
In Chinese, Japanese, or Swaheli (or any other foreign language that I'm unable to decipher), date and time might as well be shown as 輸#式~戻?も (pretty much random characters without any significant meaning to me)
There is not necessarily a ':' or a '.' in a specific place (or at all), nor any arabic numbers.

It gets even more painful if you try to account for time zones. Time zone calculations are one of the most painful things on this planet, because there is no clean standard to how daylight saving times are implemented. Different countries have different formulas of determining the actual date, which differs by as much as 3 weeks around the globe, and they use different times, too.

Thus, I decided to go the easy way and trust that whatever Subversion outputs in the <date> tag is a properly formatted, properly localised string suitable to be used as a timestamp. No parsing, no tampering, no chance of anything going wrong. Not opening Pandora's box again ;)
Title: Re: The 14 february 2007 build is out.
Post by: Biplab on February 20, 2007, 10:09:38 am
Hi Thomas,

C::B SVN is in English. So why shall we bother about other languages? :D

Daylight savings have recently been changed in some countries (Sri Lanka, Australia, etc). So they made life bit more difficult. ;)

So what have you decided on this problem? :)

Thanks & Regards,

Biplab
Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 20, 2007, 11:04:34 am
Hello Thomas,

Nice to see you are back.

Well really it has worked in the past, really really. I build CB on windows on 2 different machines (and in the past on 3). All of them have TortoiseSvn installed, none of them svn.exe. Really I never ever added svn.exe. And all of them were able to put the svn rev number in the build (proofed by the older nightly builds). But now all of them give the "0".

I will do on my laptop a test, by just reverting the autorevision.cpp to see what happens (hopefully it works together with the .h file being moved/created in another location).
Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 20, 2007, 01:57:09 pm
@Thomas.
I looked at the old autorevision.cpp and I know why it used to work. Partly you are correct the QuerySvn() never worked when there was no svn.exe, but the old code would try ou the fallback mechanisms through ParseFile()

Those 2 fallbacks are gone. I will put hem back locally on my machine and see if things are ok again, if so I would suggest, if you agree, to bring them back. I know it's ugly and hard to maintain code, put it is better then nothing.
Title: Re: The 14 february 2007 build is out.
Post by: Biplab on February 20, 2007, 01:59:01 pm
Hi Thomas,

Killerbot is correct. I can confirm his finding. In my PC, svn was not in path, but there used to be no problem in compiling and the revision number was always printed properly. I just had a look into older autorevision.cpp file.

The following line was responsible in providing the correct revision number even without using svn.
Code
    QuerySvn(workingDir, revision, date) || ParseFile(docFile, revision, date) || ParseFile(docFile2, revision, date);

Once the QuerySvn() failed, ParseFile() was called and it's parameters are as follows.

Code
    string docFile(workingDir);
    docFile.append("/.svn/entries");
    string docFile2(workingDir);
    docFile2.append("/_svn/entries");

So basically autorevision was using <WorkingDir>/.svn/entries file to provide correct revision number when svn was not in PATH. I'm quoting the following code from old autorevision code.

Code
        while(!inFile.eof() && c < 6)
            inFile >> token[c++];
        revision = token[2];
        date = token[5].substr(0, strlen("2006-01-01T12:34:56"));
        date[10] = 32;
      
And also quoting the first few lines of src/build_tools/autorevision/.svn/entries file.

Quote
8
dir
3624
https://biplab@svn.berlios.de/svnroot/repos/codeblocks/trunk/src/build_tools/autorevision
https://biplab@svn.berlios.de/svnroot/repos/codeblocks
2007-02-13T11:28:07.805641Z

So third line gives revision number and the 6th one is giving date & time.

I compiled and ran old autorevision in two places, once in Desktop and next in src folder. I'm quoting error of one case (svn not found error is present in both the cases)-
Quote
C:\Required\cbsource\src>build_tools\autorevision\autorevision.exe +int +t . autorevision.h
'svn' is not recognized as an internal or external command,
operable program or batch file.

And the file content is as follows.
Code
/*3624*/
#ifndef AUTOREVISION_H
#define AUTOREVISION_H

#define SVN_REVISION "3624"

#define SVN_DATE     "2007-02-20 10:43:54"

namespace autorevision
{
const unsigned int svn_revision = 3624;
}

#endif

When I run autorevision in Desktop, following file is generated.
Code
/*0*/
#ifndef AUTOREVISION_H
#define AUTOREVISION_H

#define SVN_REVISION "0"

#define SVN_DATE     ""

namespace autorevision
{
const unsigned int svn_revision = 0;
}

#endif

In newer autorevision this ParseFile() function has been removed which is creating problem if svn is not available in PATH.

Regards,

Biplab
Title: Re: The 14 february 2007 build is out.
Post by: killerbot on February 20, 2007, 02:44:42 pm
when re-adding the 2 ParseFile() methods, all works well again.
@Thomas : do we add them again ??

For tonights nightly I will build with my private copy of autorevision.cpp
Title: Re: The 14 february 2007 build is out.
Post by: Alturin on February 20, 2007, 09:50:40 pm
I'm thinking, why not add them? I mean, what's the worst thing that could happen? A wrong revision number being shown?
Wouldn't a wrong revision number in the theoretical case SVN decided to change it's .svn directory structure be better then the actual case of always a '0' as revision number?
Title: Re: The 14 february 2007 build is out.
Post by: thomas on February 21, 2007, 10:51:32 am
when re-adding the 2 ParseFile() methods, all works well again.
@Thomas : do we add them again ??

For tonights nightly I will build with my private copy of autorevision.cpp
Please don't. It were my fallback solutions that caused the problems why we use XML now. Although the intent was good, the idea was bad ;)
We should keep our hands off parsing that stuff, seriously.

First we had people with other languages (2-3 French, 2-3 Turkish, and 1-2 Russian, but I think it applies to all) who could not get it to work, because their locale would cause the date to be written in some format that my fallback parser did not understand. That was bad enough already.

But then, even worse, the entries file format was changed, so my fallback implementation would not even work in English locale any more! Everybody who never bothered having Subversion installed properly (because the fallback worked nicely) started yelling "arg! the build is broken!" over night, when it really wasn't. It was just that the fallback did not work with the new entries format.

So, the new implementation uses Subversion's XML output format, which is hopefully standardised and immutable (or at least backwards-compatible) so we never see any such thing again.
I'm very much disinclined to use a custom-made hack and take the responsibility for keeping up with locales, time zones, and file format changes when there is really a clean, reliably working solution, only because some people don't want to install Subversion (or have it in path).
It's no problem really... those who don't want to install Subversion can use a source tarball (when one is available), or they will have "Revision 0".

I don't think requesting Subversion is an outrageous demand, either. Without Subversion, there is no way you can check out a the sources, anyway. No, please don't tell me there is TortoiseSVN and RapidSVN and whatever :)
Using Tortoise/RapidSVN or similar is always nasty tampering, which may work or may not (remember the _svn issue they had last year). Granted, it usually works really nicely (I use it all day, and I very very rarely see an issue), but it is not the one real, canonical thing.
Title: Re: The 14 february 2007 build is out.
Post by: gjsmo on February 21, 2007, 10:07:35 pm
Yes, hitting the < button works, but this should be done automatically. If there is enough room to see all the tabs, I want to see them!