I've updated the Wiki pages with some more info:
Installing_Code::Blocks_nightly_build_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_nightly_build_on_Mac_OS_X)
Installing_Code::Blocks_from_source_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=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.
I've updated the Wiki pages with some more info:
Installing_Code::Blocks_nightly_build_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_nightly_build_on_Mac_OS_X)
Installing_Code::Blocks_from_source_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=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.
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!!!
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:
# 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