- If trying to compile while debugging in progress, ask to stop debugging (previously it wasn't allowed) - needs testing on windows
(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! :)(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... :(
- 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:
--- 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
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)
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. :-(QuoteAnyway, 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. :-(
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.
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)
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)
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.
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 ?
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
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. :-(QuoteDoes 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.
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.
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 also heard the toolbar problem was fixed in SVN
"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."
Could you guys please include the following into the next nightly build, it needs to be placed in lexer_squirrel.xml: