User forums > General (but related to Code::Blocks)
Old links on Mac OS X page.
stahta01:
http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X#Download_the_source_code_2
Many old stuff as in broken links and berlios.de URL usage.
Tim S.
afb:
--- Quote from: stahta01 on June 12, 2015, 03:22:24 am ---http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X#Download_the_source_code_2
Many old stuff as in broken links and berlios.de URL usage.
--- End quote ---
It's a wiki, go edit it. ;-) But seriously, the berlios links and outdated instructions are only half of the problem...
The biggest issue is that wxWidgets on OS X is stuck between 2.8 (10.6/32-bit only) and 3.0 (10.9/64-bit only).
The workaround (for now), will be to run with wxGTK under XQuartz.
oBFusCATed:
Why should we care about 32bit anymore?
afb:
--- Quote from: oBFusCATed on June 20, 2015, 12:59:04 pm ---Why should we care about 32bit anymore?
--- End quote ---
The problem is that the wxWidgets 2.8 GUI (wxMac) *only* works in 32-bit, due to Carbon.
So it needs to be updated to wxWidgets 3.0 (wxOSX) that also works in 64-bit, with Cocoa.
afb:
Seems that the timing for wxGTK wasn't all the best, as X11 GTK+ support was just removed in Homebrew:
https://github.com/Homebrew/homebrew/pull/39868
This means it (gtk+) cannot be used for wxGTK anymore. Otherwise it was a reasonable workaround for OS X:
https://github.com/afb/homebrew/commit/6bad8b5
So that only leaves wxWidgets 3.0 then, I suppose... I haven't checked how far away that is on trunk, though ?
Doing a custom build of X11 GTK+ just for Code::Blocks is possible of course, if one wants to continue that route.
Navigation
[0] Message Index
[#] Next page
Go to full version