Hi,
this is nice, it would be even nicer if it could be mantained by someone with commit access over svn,
the unix cbp's are almost the same, with some differences, so you could
a) maintain a set of patches to output -mac.cbp's based on the -unix.cbp's
b) maintain a different set of projects (lot of burden maintenance)
c) maintain a sed script to output -mac.cbp's based on the -unix.cbp's.
d) maintain a set of build scripts (squirrel) for the -unix.cbp's (this is the one I like most)
some things to note in the projects attached:
1) you use
<Option output="devel/libwxscintilla.dylib" prefix_auto="0" extension_auto="0" />
but it is not necessary, the idea is to use prefix_auto="1" and extension_auto="1" so CodeBlocks guesses the prefix and extension automatically,
so here, we cut the "diff" a bit,
2) I can see that you use sometimes <Add option="`wx-config --libs`" /> in both the Projects and the Targets, it is not necessary to be in both, just use one of the two, and leave the same as the -unix.cbp's
3) there is <Add option="-D__WXMAC__" /> usage,
question: doesn't wx-config --cxxflags defines that automatically?
4) I see inclusion of <Add directory="/usr/lib" /> and <Add directory="/usr/local/lib" />,
for which library is this necessary? if for wx, that's not good,
the problem in hard-coding this system path in the project is that, for example, if you want to use the wx from MacPorts (/opt/local/lib) the above path will override it; I think it's better to leave the user to define those system paths in their own linker paths.
linking to /usr/lib/libSystem.dylib directly is rather OK because you don't bring all the paths to the linker