There's still a minor issue: At about line 162-163 of the script you generate a list of the compiled tools to pass on to lipo in order to create universal binaries:
echo buildtools: Creating fat binaries.
utils=`make printutils` `EXESUFFIX_OVERRIDE=.debug make printutils`
The problem is that that fails if you aren't doing a debug build. I've managed to fix that by explicitly checking for the debug option and changing the way the utils variable gets created as a result, but I'm not sure what, if anything, that'll break down the road:
echo buildtools: Creating fat binaries.
if [ $builddebug == 1 ]; then
utils=`make printutils` `EXESUFFIX_OVERRIDE=.debug make printutils`
else
utils=`make printutils`
fi
Which brings me to my next point:
TX, on 21 March 2012 - 07:10 PM, said:
LSDNinja, do you have a SourceForge account? It has been proposed to give you svn commit access for the sake of maintaining OS X support, and after some consideration I've decided to allow it. So, if you don't already have one, please create a SourceForge account and I'll add you as a project member.
I'm... not quite sure how I feel about that. I don't know what else I can really contribute since my expertise begins and ends at relatively minor script hacks, anything code-related and I'm completely out of my depth :/ The other major reason why I'm uneasy about being given such responsibility is because I only have the most basic understanding of what I'm messing with here and it makes me feel a little better to be able to have anything I come up with peer reviewed before it gets committed in case a better solution exists. In any case, my sourceforge.net account is admiral_lsd if you still want to add it.
Tetsuo, on 22 March 2012 - 03:19 AM, said:
To tell the truth, I don't really mind it. It's great for the small typos I make all the time on account of my typing style. The downside is, of course, that you have to be on your toes a bit more in case it corrects something you misspelt on purpose.
Also, another couple of issues I've noticed: When Hendricks changed the conditionals to make 10.5 the minimum supported version and/or disable the powerpc build on Snow Leopard and above, it resulted in the 64-bit build not being disabled on 10.5 (because build64=0 fell into a place that only got executed on <10.5). I think I've fixed that:
if [ `expr $darwinversion \< 9` == 1 ]; then
echo OS X 10.5 is the minimum requirement for building.
exit 1
fi
if [ `expr $darwinversion \= 9` == 1 ]; then
build64=0
fi
if [ `expr $darwinversion \> 9` == 1 ]; then
buildppc=0
fi
but perhaps someone here has a more elegant solution.
Secondly, I've noticed an odd discrepancy between PowerPC builds compiled on an actual PowerPC Mac and those cross-compiled on an Intel Mac. The cross-compiled builds seem fine, building and linking with no apparent errors and they appear to work when you run them through Rosetta, but transfer them to a PowerPC Mac and they crash. I'll do some more digging with a debug build (it crashes properly meaning an accurate backtrace shouldn't be hard to generate), but it'll probably take some time since debug builds require jumping through a few hoops to get working right.
Help
Duke4.net
DNF #1
Duke 3D #1
