Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on April 01, 2006, 09:48:36 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://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z
For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z
The 01 April 2006 build is out.
- Windows : http://download.berlios.de/codeblocks/CB_20060401_rev2288_win32.7z
- Linux :
http://download.berlios.de/codeblocks/CB_20060401_rev2288_ubuntu.deb
http://download.berlios.de/codeblocks/CB_20060401_rev2288_fc4.rpm (not yet)
Resolved Fixed:
- (Add wxbitmapbutton support and Update the project file for adding wxbitmapbutton support)
- Fix the bug on the wxStatusbar code generated by wizard
Regressions/Confirmed/Annoying/Common bugs:
- toolbar-images-not-changing-state (is a wx problem)
- there are several issues with Code Completion (is being redesigned : work in progress)
-
Hi killerbot,
I just downloaded this windows build, until now I used the official RC2. This new CodeBlocks starts very slow on my computer. It takes ~5s to start up. Is this normal behaviour? The old RC2 started very quick.
Regards,
bszente
-
Howdy,
It has been ages since I used RC2, so I have no idea if indeed things got slower (at startup) or not. But for sure thigns have got better.
Just make sure you don't mix RC2 and nightly, my personal advice : remove RC2 ;-)
Cheers,
Lieven
-
Well, this build seems important enough to synch with, so I guess I will download this one...
-
Hello killerbot,
I have made a video about the following problem (C::B crash with floating windows)
http://forums.codeblocks.org/index.php?topic=2749.msg21949#msg21949
You can find it here: http://www.badongo.com/file/415441
I don't understand why you are not able to reproduce this behavior because I have reproduced this problem on three diffrent computers.
Before doing my test, I have:
- deleted my default.conf file
- use CB_20060401_rev2288_win32.7z, wxmsw26u_gcc_cb.7z archive
You will see in the video that floating windows disappear, I don't why (it is probably a problem with my capture software) but I hope it will help you to reproduce this problem.
Thanks and have a nice day.
C::B used: Version 1.0 revision 2288 (gcc 3.4.4 Windows/unicode, build: Apr 1 2006 21:23:04)
-
I have made a video about the following problem (C::B crash with floating windows)
http://forums.codeblocks.org/index.php?topic=2749.msg21949#msg21949
Have a look here:
http://forums.codeblocks.org/index.php?topic=2582.0 (http://forums.codeblocks.org/index.php?topic=2582.0)
With regards, Morten.
-
killerbot, when do you think you will have a libunicows build of C::B?
-
not in the coming 2 weeks : next week I am abroad all week for work (again), France this time.
-
not in the coming 2 weeks : next week I am abroad all week for work (again), France this time.
Oh, well have a safe trip next week!
-
Please check RSS
"01 March 2006" rev 2288
:shock:
-
I have made a video about the following problem (C::B crash with floating windows)
http://forums.codeblocks.org/index.php?topic=2749.msg21949#msg21949
Have a look here:
http://forums.codeblocks.org/index.php?topic=2582.0 (http://forums.codeblocks.org/index.php?topic=2582.0)
With regards, Morten.
So I am not mad :wink:
Why don't you manage to reproduce it killerbot?
I am going to look for another bugs. I am a mad tester :twisted:
Thanks and have a nice day.
-
Please check RSS
"01 March 2006" rev 2288
:shock:
thx
-
Anyone can check if Tools | "Any menu item" is working?
-
Noticed that when "Launch tool in a new console window and wait for a keypress when done" is not check it will not show the application. Can anyone please verify?
-
Why don't you manage to reproduce it killerbot?
I guess he's using wxWidgets 2.6.3 (RC or release). The bug has disappeared with this version of wxWidgets - so he couldn't reproduce.
With regards, Morten.
-
Why don't you manage to reproduce it killerbot?
I guess he's using wxWidgets 2.6.3 (RC or release). The bug has disappeared with this version of wxWidgets - so he couldn't reproduce.
With regards, Morten.
I don't have it with wx 2.6.2 neither
-
The 01 April 2006 build is out.
...
Resolved Fixed:
- Fix the bug on the wxStatusbar code generated by wizard
and introduced another bug :)
it would be nice, if one would test the changes before commiting to svn :shock:
change
SetMenuBar(new wxStatusBar(this,-1));
to
SetStatusBar(new wxStatusBar(this,-1));
otherwise you'll get a compile error
-
Just make sure you don't mix RC2 and nightly, my personal advice : remove RC2 ;-)
Hi Lieven,
I unsinstalled RC2, I deleted every C::B related file. I even deleted everything related to C::B from the registry too. After this done, I simply unzipped the C::B from this build, to the standard installation path along with the wxWidgets DLL and mingwm10.dll.
That 5 seconds startup time did not disappear. I attached a screenshot too. You can see there, that I started consecutively 4 times Code::Blocks and closed it. Each time the startup duration is 5 second, and the CPU usage is ~100%. After this short time everything goes back to normal, but it is realy bothering this long startup time.
... But for sure thigns have got better.
Definitelly. There are numeruous new good and handy features. That's why I'm upgrading.
But really, am I the only one, who experience this long startup time? It might happen the the problem relies at my side... :?
Regards,
bszente
[attachment deleted by admin]
-
bszente: no, you're not the only one to experience the problem, and I'm concerned about it.
Here's an extract of a PM I sent to Yiannis:
* Performance issues:
I have spent some time trying to find a profiler other than gprof (because it's known limitations).
I couldn't find any free win32 one (I use CodeAnalyst from AMD which is really good but only works with VC on win32, and for linux it works with gcc but requieres kernel recompilation).
I became very concerned about the hotspot:
-C::B initial load is very slow (it is more than Firefox :shock:). On first load it takes 15 seconds on this machine, and 5 seconds on subsequents loads.
That is crossing the barrier between acceptable, but it's still not much.
The problem relies when I need to use C::B at univ., because the programs can only be loaded from the lan. It takes 50 seconds :shock: to load, while almost any other program takes less (SciTE takes 1 seconds).
At first I thought that it was the lexers, but they are part responsible only. The lexers usually take a constant time of 4 seconds on every load (that is, when running C::B or opening the Editor dialog).
About that, couldn't the lexers be loaded only on C::B load instead of on every Editor dialog aperture (cached)?
But after all I noticed probably most time is spent in stub dll loading, almost 0.8~2 seconds for each plugin dll, which when added to lexers, I reach the 15 seconds that C::B tooks on first load (on my pc: Athlon 64 3000, 512MB).
I don't know other way to solve that unleast using the GCC4 feature visibility=hidden. See here: http://gcc.gnu.org/wiki/Visibility
-
-C::B initial load is very slow (it is more than Firefox Shocked). On first load it takes 15 seconds on this machine, and 5 seconds on subsequents loads
Firefox runs prelink after installing. If you do that after compiling Code::Blocks, it is a lot faster, too. On my machine, it loads in about three seconds on the first run without me caring to use the visibilty flag at all.
-
-C::B initial load is very slow (it is more than Firefox Shocked). On first load it takes 15 seconds on this machine, and 5 seconds on subsequents loads
Firefox runs prelink after installing. If you do that after compiling Code::Blocks, it is a lot faster, too. On my machine, it loads in about three seconds on the first run without me caring to use the visibilty flag at all.
Good to know, it isn't not the point btw.