Code::Blocks on Mac OS X

[afb]

I've updated the Wiki pages with some more info:
Installing_Code::Blocks_nightly_build_on_Mac_OS_X
Installing_Code::Blocks_from_source_on_Mac_OS_X

Currently there are three major ways to install C::B:

1) Download the binary package and run it. Easy :-)
wxWidgets libraries are included in the app bundle.

/Developer/Applications/CodeBlocks.app

2) Build the entire thing in /usr/local, from scratch...
This currently requires some tweaks and autotools-fu.

/usr/local/bin/codeblocks

3) Download and build using the DarwinPorts system.
Somewhat of a pain until Portfile is included upstream.

/Applications/DarwinPorts/CodeBlocks.app
/opt/local/bin/codeblocks

BTW:
The advantages of DarwinPorts is that it can build
both wxMac and wxGTK versions, and that all the
dependencies and updates from SVN are automated.
It can also build packages, which might be interesting.

Code

port install codeblocks

[Auria]

i'm maybe a little offtopic but i've some big problem with code::blocks on mac...

basically i changed the console to Terminal.app and programs run fine. The only problem - if i click the red X button to stop the process, my computer almost shuts down! (dock disappears, screen goes blue, then fades down - but quickly finder starts again) i have no idea what this can be i've never seen this behaviour anywhere - any idea?à

(BTW thanks for your efforts in this project  )

[afb]

basically i changed the console to Terminal.app and programs run fine. The only problem - if i click the red X button to stop the process, my computer almost shuts down! (dock disappears, screen goes blue, then fades down - but quickly finder starts again) i have no idea what this can be i've never seen this behaviour anywhere - any idea?

Confirmed.

Do not set your console to /Applications/Utilities/Terminal.app ("Doctor, it hurts when I do this"). It starts in the background, and that "X" will kill your entire login instead... (quitting all your apps)

It also uses "LD_LIBRARY_PATH" instead of "DYLD_LIBRARY_PATH" like it should on Darwin, so the console settings in Code::Blocks will need some fixing for Mac OS X: i.e. it's a current bug.

[Paco.Blasco]

I've updated the Wiki pages with some more info:
Installing_Code::Blocks_nightly_build_on_Mac_OS_X
Installing_Code::Blocks_from_source_on_Mac_OS_X

Currently there are three major ways to install C::B:

1) Download the binary package and run it. Easy :-)
wxWidgets libraries are included in the app bundle.

/Developer/Applications/CodeBlocks.app

2) Build the entire thing in /usr/local, from scratch...
This currently requires some tweaks and autotools-fu.

/usr/local/bin/codeblocks

3) Download and build using the DarwinPorts system.
Somewhat of a pain until Portfile is included upstream.

/Applications/DarwinPorts/CodeBlocks.app
/opt/local/bin/codeblocks

BTW:
The advantages of DarwinPorts is that it can build
both wxMac and wxGTK versions, and that all the
dependencies and updates from SVN are automated.
It can also build packages, which might be interesting.

Code

port install codeblocks

Hi afb:

I didn't see on my DarwinPorts a dports/devel folder. Can you tell me the absolute path? I supposed you have the "standard" folder: /opt
By the other side, I was probing the x86 and it crashed. If you want, I can send you the crashing info.
Thanks a lot all your effort!!!

[afb]

I didn't see on my DarwinPorts a dports/devel folder. Can you tell me the absolute path? I supposed you have the "standard" folder: /opt

Sure: "~/dports" :-) - you need to create the folder yourself, first time:
http://darwinports.opendarwin.org/docs/ch03s05.html#local_repository

My sources.conf looks like this:

Code

# To enable your local ports repository, uncomment and customize the
# following line to point at your local dports directory
# Example: file:///Users/landonf/misc/darwinports/dports
file:///Users/afb/dports
# To get darwinports from the opendarwin rsync server use:
# rsync://rsync.darwinports.org/dpupdate/dports
rsync://rsync.darwinports.org/dpupdate/dports

By the other side, I was probing the x86 and it crashed. If you want, I can send you the crashing info.

Please report as bugs on BerliOS (when back), but I haven't started debugging x86 myself yet - and there are known issues on PPC too... Will try to detail some of the more common ones on the Wiki page

[Game_Ender]

It looks as if the portfile install both the wxGTK and wxMac versions by default, can this behaviour be disabled?  I don't want to use GTK on OS X, I use it enough with linux.

[afb]

It looks as if the portfile install both the wxGTK and wxMac versions by default, can this behaviour be disabled?  I don't want to use GTK on OS X, I use it enough with linux.

It would use "wxMac" for +macosx variants, and "wxGTK" for +puredarwin variants ?
(I am using it both to test the X11 build on Mac OS X, and to compare the versions...)

Like these screenshots: http://www.algonet.se/~afb/wx/codeblocks.html#rev2921

But the default Portfile should instead use the official "wxWidgets" port (hard-coded Mac),
I think I commented out wxMac ? (feel free to comment out wxGTK as well, if you like...)

[afb]

The official Portfile for wxWidgets have moved onto here instead, now that Darwin is dead:
http://trac.macports.org/projects/macports/browser/trunk/dports/graphics/wxWidgets/Portfile

[Game_Ender]

Thank you for your work afb, hopefully I will get a chance to try this out soon.