Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on February 06, 2008, 09:50:58 pm

Title: The 06 February 2008 build (4866) is out.
Post by: killerbot on February 06, 2008, 09:50:58 pm
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works (http://forums.codeblocks.org/index.php/topic,3232.0.html).

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx287.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc421.7z

The 06 February 2008 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20080206_rev4866_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 06 February 2008 build (4866) is out.
Post by: jens on February 06, 2008, 09:57:55 pm
Binaries for debian i386, amd64 and sources (tar-balls also usable on other platforms) can be found in my repository (see signature).
Title: Re: The 06 February 2008 build (4866) is out.
Post by: pasgui on February 07, 2008, 01:19:02 am
Build for Ubuntu i386/amd64 can be found here (http://lgp203.free.fr/spip/spip.php?article1)

Best regards, pasgui
Title: Re: The 06 February 2008 build (4866) is out.
Post by: rhf on February 07, 2008, 03:07:22 am
  • If trying to compile while debugging in progress, ask to stop debugging (previously it wasn't allowed) - needs testing on windows

I experimented briefly with this on Windows XP, and it appears to work properly. I really like this feature and hope that it continues to work well under more exhaustive tests. I do have two questions:

(1) When trying to compile while debugging, the Information box asks, "Do you want to stop the debugger now?" There are three options: Yes, No and Cancel. What is the difference between No and Cancel?

(2) How difficult would it be to provide a similar feature for closing a console output window when re-compiling? I am constantly getting caught trying to re-compile with the window open.

Thanks very much for this nice feature.
Title: Re: The 06 February 2008 build (4866) is out.
Post by: MortenMacFly on February 07, 2008, 07:51:59 am
(1) When trying to compile while debugging, the Information box asks, "Do you want to stop the debugger now?" There are three options: Yes, No and Cancel. What is the difference between No and Cancel?
There is no difference. Maybe I should have used a OK/Cancel combination to avoid confusion... :(
Title: Re: The 06 February 2008 build (4866) is out.
Post by: cfdev on February 07, 2008, 10:55:24 am
Hi all

Package for Slackware 12.0 -> Here (http://sourceforge.net/projects/slackfr-packs/)

good day :D
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Xaviou on February 07, 2008, 12:43:14 pm
Ubuntu 7.04 -> 7.10 Amd64 tar.gz archive (containing '.deb' installers builds with wx2.8.7) can be found here (http://www.esnips.com/web/CodeBlocks)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: thomas on February 07, 2008, 06:03:20 pm
(1) When trying to compile while debugging, the Information box asks, "Do you want to stop the debugger now?" There are three options: Yes, No and Cancel. What is the difference between No and Cancel?
There is no difference. Maybe I should have used a OK/Cancel combination to avoid confusion... :(
Maybe there should be no dialog at all! :)
Well, at least it is not as annoying as it used to be. Luckily "yes" is the default button, too, so you can hit "enter" to finally get the IDE to do what you asked for.
Title: Re: The 06 February 2008 build (4866) is out.
Post by: afb on February 08, 2008, 12:21:01 am
- Mac OS X: (10.4 and 10.5 Universal Binary, using bundled wxWidgets 2.8.7)
  http://prdownload.berlios.de/codeblocks/CB_20080206_rev4866_mac287.zip
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Auria on February 08, 2008, 02:19:22 am
- Mac OS X: (10.4 and 10.5 Universal Binary, using bundled wxWidgets 2.8.7)
  http://prdownload.berlios.de/codeblocks/CB_20080206_rev4866_mac287.zip


afb, my C::B builds on mac are unusable, because of two bugs, wxDynamicLibrary not working on dylibs, and combos in toolbars not appearing. Both have been confirmed on the wx bug tracker - But your builds are free of them?  :? I'm a bit amazed at your magical bug-fixing abilities :lol:

Anyway, good job, as usual  :)

Someday, the C::B website should be updated, it says only Linux and Windows are supported (I'm not sure how good mac support is ATM but I think it's usable (apart from some wizards perhaps)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: afb on February 08, 2008, 09:31:39 am
afb, my C::B builds on mac are unusable, because of two bugs, wxDynamicLibrary not working on dylibs, and combos in toolbars not appearing. Both have been confirmed on the wx bug tracker - But your builds are free of them?  :? I'm a bit amazed at your magical bug-fixing abilities :lol:

Hmm, when would the wxDynamicLibrary bug kick in ? If they are loadable libraries, then they would probably be .bundle (or .so) rather than .dylib - since .dylib aren't loadable at runtime (only linktime) ? I don't have any problem with this when building with ./configure && make, did you have any more details (or the Bug number) on where it would apply ? Maybe it is when trying to build Code::Blocks with itself ?

As for the combos-in-toolbars, I have patched my wxWidgets configuration so that what you get with configure matches (somewhat) what you get with Xcode - keeping them synched is an upstream problem. (and the native Mac toolbar doesn't work with popup menus in the current wxWidgets implementation...)

Code: [Select]
--- include/wx/mac/carbon/chkconf.h 2007-05-14 11:09:36.000000000 +0200
+++ include/wx/mac/carbon/chkconf.h 2007-05-21 10:59:19.000000000 +0200
@@ -55,7 +55,7 @@
  */
 
 #ifndef wxMAC_USE_NATIVE_TOOLBAR
-    #define wxMAC_USE_NATIVE_TOOLBAR 1
+    #define wxMAC_USE_NATIVE_TOOLBAR 0
 #endif
 
 #endif

Quote
Anyway, good job, as usual  :)

Thank you! I haven't been able to do much development, but the monthly builds have been "working" OK.

PS. It is also available in MacPorts (http://www.macports.org) as port "codeblocks-devel", for both wxMac (Aqua) and wxGTK (X11)...

Quote
Someday, the C::B website should be updated, it says only Linux and Windows are supported (I'm not sure how good mac support is ATM but I think it's usable (apart from some wizards perhaps)

Depends on your definition of "support", I guess ? But yeah, it's been updated a bit on the Wiki for instance
Title: Re: The 06 February 2008 build (4866) is out.
Post by: MortenMacFly on February 08, 2008, 09:44:57 am
Quote
Anyway, good job, as usual  :)
Thank you! I haven't been able to do much development, but the monthly builds have been "working" OK.
Nice one! :-) I wish I could try MAC-OS someday. Do you see any chance of running it in a VM somehow? I would be willing to buy MAC-OS, but not a MAC - thjis is just by far too expensive (even at eBay) for me. :-(
Title: Re: The 06 February 2008 build (4866) is out.
Post by: hangl on February 08, 2008, 10:16:11 am
It takes a long time (about 1~2 minutes) to open a cpp file when I double click   it in explorer.And the explorer was frozen until the file was opend in CB.

WinXp SP2
Title: Re: The 06 February 2008 build (4866) is out.
Post by: afb on February 08, 2008, 10:56:28 am
Nice one! :-) I wish I could try MAC-OS someday. Do you see any chance of running it in a VM somehow? I would be willing to buy MAC-OS, but not a MAC - thjis is just by far too expensive (even at eBay) for me. :-(

Sorry, you cannot legally run Mac OS X in a virtual machine - except on Mac OS X itself...
It's not that it would be impossible, just that Apple does not want you to switch hardware.

But I suppose you could get someone with a Mac to let you borrow it - over VNC or so ?
Or ask the guy in the Apple Store for a demonstration of the url "www.codeblocks.org" ;-)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: codemania on February 08, 2008, 01:38:14 pm
Hi!
Codeblocks prints well on Windows but on Linux I can't do it.

I have a print driver installed.
On Linux I print well with other software.

Codeblocks menu.
File>>Print...


codemania
Title: Re: The 06 February 2008 build (4866) is out.
Post by: MortenMacFly on February 08, 2008, 01:57:35 pm
It's not that it would be impossible, just that Apple does not want you to switch hardware.
Huh? I thought Apple managed to create a X86 compatible version of the OS. Does that mean although it could run on a native X86 hardware (VM) then it's forbidden by the MAC-OS EULA when I buy the MAC-OS software? So why do they sell it then as standalone product?

But I suppose you could get someone with a Mac to let you borrow it - over VNC or so ?
I don't know people with a MAC unfortunately. And those I meet that have one won't allow me VNC on it... for sure. ;-)

Or ask the guy in the Apple Store for a demonstration of the url "www.codeblocks.org" ;-)
LOL - that would be an option, indeed.

Ps.: We are getting quite off-topic... sorry.
Title: Re: The 06 February 2008 build (4866) is out.
Post by: wobien on February 08, 2008, 03:47:59 pm
The parser used to never parse on my startup but now it seems to. 
I didn't download the 4861 build, but in the 4866 build I still have to do "Re-parse now" to get the symbols in my Default workspace parsed after startup. (Windows XP)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: afb on February 08, 2008, 04:10:54 pm
I thought Apple managed to create a X86 compatible version of the OS.
They did, yes. Unofficially in 2001 and officially since 2005... (Mac OS X version 10.4.4)

Quote
Does that mean although it could run on a native X86 hardware (VM) then it's forbidden by the MAC-OS EULA when I buy the MAC-OS software?
Yup.

Quote
So why do they sell it then as standalone product?
So that people who bought a Mac with a previous OS version pre-installed can upgrade ?
Title: Re: The 06 February 2008 build (4866) is out.
Post by: thomas on February 08, 2008, 05:07:33 pm
Is it just me, or is Apple even more abusive than Microsoft? You'd think they'd be happy if anyone buys their crap at all, but apparently not.
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Auria on February 08, 2008, 05:24:10 pm
Well one point for Apple not supporting install of OS X on all computers is one of driver issues - everyone makes windows drivers so windows does run everywhere, and linux can afford to be a bit more buggy at drivers (or harder to setup) since it's usually free and community-maintained, but not everyone makes mac drivers and Apple can't write them all by themselves. And they couldn't advertise mac OS X installs on the average PC without drivers, cause users would try it, it wouldn't work, OS X would get a bad reputation, etc. that's how they achieve the rock stability that makes OS X users love it

HOWEVER, I think *forbidding* it is totally abusive. They could just have marked it unsupported (and of course it's more money for them this way)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Auria on February 08, 2008, 05:27:41 pm

Hmm, when would the wxDynamicLibrary bug kick in ? If they are loadable libraries, then they would probably be .bundle (or .so) rather than .dylib - since .dylib aren't loadable at runtime (only linktime) ? I don't have any problem with this when building with ./configure && make, did you have any more details (or the Bug number) on where it would apply ? Maybe it is when trying to build Code::Blocks with itself ?

As for the combos-in-toolbars, I have patched my wxWidgets configuration

Well by default the C::B build system generates .dylibs and not bundles or so files on my computer (not sure how to change that either). But .dylibs ARE definitely loadable at runtime, for instance dlopen() opens them just fine. I'm not sure why on your computer libraries build different from mine, it's perhaps a different version of autotools or something
The wxMac maintainer said wxDynamicLibrary would be re-written in the future to offer better support, anyway, so that problem will be fixed by itself.

I also heard the toolbar problem was fixed in SVN
Title: Re: The 06 February 2008 build (4866) is out.
Post by: MortenMacFly on February 08, 2008, 08:48:11 pm
Quote
Does that mean although it could run on a native X86 hardware (VM) then it's forbidden by the MAC-OS EULA when I buy the MAC-OS software?
Yup.
Ah - ok. I honestly was not aware of that. I see reasons to do so from an Apple point of view but for me this means my dreams of having MAC OS in a VM are gone. :-(

So that people who bought a Mac with a previous OS version pre-installed can upgrade ?
Ok... sounds obvious. So this would mean they basically sell updates only.

Thanks a lot for that information! :D

With regards, Morten.
Title: Re: The 06 February 2008 build (4866) is out.
Post by: afb on February 08, 2008, 10:06:24 pm
Well by default the C::B build system generates .dylibs and not bundles or so files on my computer (not sure how to change that either). But .dylibs ARE definitely loadable at runtime, for instance dlopen() opens them just fine.

I think the main difference was with dlclose (as in: not available with dylib)
But I also think that with Mac OS X 10.5 up, they are both the same now...
(dyld is a rather complex subject). But e.g. Perl and Python uses -bundle.
It's possible that -dylib can be made to work for plugins too, but usually isn't.

Quote
I also heard the toolbar problem was fixed in SVN

Good to hear, maybe it can be patched in to wxWidgets 2.8 too then...


Quote from: http://developer.apple.com/releasenotes/DeveloperTools/RN-dyld/index.html
"In prior versions of Mac OS X only bundles (file type MH_BUNDLE) could be unloaded.
In Mac OS X 10.5 dynamic libraries (file type MH_DYLIB) can also be unloaded when using dlopen/dlclose."
Title: Re: The 06 February 2008 build (4866) is out.
Post by: zortich on February 09, 2008, 12:17:00 am
Code completition   :shock: is working awful.
Where is no code completion for #include <X11/Xlib.h> is available.
What about to improve it?
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Wahooney on February 10, 2008, 12:46:25 pm
Could you guys please include the following into the next nightly build, it needs to be placed in lexer_squirrel.xml:
<Style name="Verbatim String"
   index="13"
   fg="0,0,255"/>

For those not in the know, it adds verbatim strings (ie. @"Hi, I'm a verbatim string") to the squirrel lexer.

Thanks guys :)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Biplab on February 10, 2008, 02:42:51 pm
Could you guys please include the following into the next nightly build, it needs to be placed in lexer_squirrel.xml:

Added in rev 4869.  :)
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Wahooney on February 10, 2008, 02:45:30 pm
Thanks, Biplab :mrgreen:
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Grom on February 10, 2008, 09:19:42 pm
Is any way to write a plugin under the Windows, which will automatically install new nighties. Actually after some manipulations my suse  10.3 do this...
Title: Re: The 06 February 2008 build (4866) is out.
Post by: JGM on February 11, 2008, 03:10:39 am
using repositories on linux distros is really easy, on windows is another story
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Grom on February 11, 2008, 05:18:58 pm
That is why I am talking about the updater plugin form windows. Have no time ti implement it by my self. In fact it can be done easily in Java and connected to the C::B. One weak of part time work.
Title: Re: The 06 February 2008 build (4866) is out.
Post by: JGM on February 11, 2008, 05:43:59 pm
I don't think that using java would be very welcomed. that would introduce ... you know
Title: Re: The 06 February 2008 build (4866) is out.
Post by: dannyyy on February 11, 2008, 07:20:35 pm
I vote "NO" for JAVA code on Code::Blocks sources  :lol:
Title: Re: The 06 February 2008 build (4866) is out.
Post by: Grom on February 11, 2008, 08:08:24 pm
Ok then write the plugin in C++. :shock: