Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
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
--- End code ---
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:
--- Quote from: Auria on September 12, 2006, 01:13:08 am ---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?
--- End quote ---
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:
--- Quote from: afb on September 11, 2006, 11:56:30 pm ---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
--- End code ---
--- End quote ---
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:
--- Quote from: Paco.Blasco on September 12, 2006, 09:36:16 am ---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
--- End quote ---
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
--- End code ---
--- Quote ---By the other side, I was probing the x86 and it crashed. If you want, I can send you the crashing info.
--- End quote ---
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
Navigation
[0] Message Index
[#] Next page
Go to full version