summaryrefslogtreecommitdiff
path: root/os/macosx/Makefile.setup
AgeCommit message (Collapse)Author
2006-12-28(svn r7588) -Change: [OSX] removed the flag JAGUAR since it didn't work anywaybjarni
Also removed all the Makefile code regarding this flag since it's no longer needed Removed documentation about special limitations regarding running the game on OSX 10.2 OpenTTD now officially needs OSX 10.3.9 to work correctly (the trunk needed that for months)
2006-05-27(svn r4989) -Fix: make the OSX Makefile stuff to work with the compile-farmtruelight
2006-05-27(svn r4987) Feature: Merged YAPF into trunk. Thanks to devs for continuous ↵KUDr
support and users for testing.
2006-03-29(svn r4149) -Codechange: [OSX] rewrite of how universal binaries are compiledbjarni
Now OSX stores object files in .OSX and instead of making FAT object files, there are one for each architecture Each architecture got their own targets to make a non-FAT binary and in the end, lipo will merge them into one binary It's now possible to select which architectures you want to support by defining OTTD_PPC, OTTD_PPC970 (G5) and/or OTTD_i386 All combos are supported. UNIVERSAL_BINARY and TRIPLE_BINARY can still be used even though it's possible to gain the same result by using the new flags Making a universal build when you already got part of it compiled (say the PPC part), it will reuse it and only compile the i386 part to save time Note: in some cases when you switch flags, you risk that openttd is not updated. Delete it and try again. The Makefile can't solve this except if it forces linking each time This fixes: FS#87 universal binary building borked in 0.4.7 Now universal binaries work on OSX 10.3.9 again Building universal binaries no longer needs to store flags in Makefile.config as the new design makes it possible to figure everything out automatically
2006-03-24(svn r4076) Back out r4074. It doesn't work and leads to make endlessly ↵tron
calling itself. NOTE: Delete Makefile.config to recover.
2006-03-23(svn r4074) -Feature: [Makefile] the makefile can now detect if iconv is ↵bjarni
present in the system if detected, WITH_ICONV will be defined in the C code WITH_ICONV is also added to Makefile.config OSX do not use this flag setting in Makefile.config, as it is set at compile time based on target OS version the actual C code is not changed as the current iconv code is hardcoded for OSX and would break if any other OS got iconv This detection system is by request of Darkvater
2006-03-22(svn r4019) -Fix: [OSX] stopped using iconv for 10.2.8, since it was added ↵bjarni
in 10.3 this have the sideeffect that 10.2.8 will still have the "failure to save with certain chars in the filename bug", but at least it can compile again
2006-03-15(svn r3884) renamed TRIPPLE_BINARY to TRIPLE_BINARYbjarni
2006-03-15(svn r3882) -Codechange: [OSX] changed the way universal and tripple ↵bjarni
binaries are build Instead of compiling a binary for each arch and then join them in the end, each .o file is now compiled as a fat file This means that the makefile will not call itself to make a binary for each target and we don't have to make clean between each build it also means that if one file changed, we don't have to recompile all files Another benefit is since it's handled at .o level and though LDFLAGS, no special code is needed if we decide to compile more binaries (like a lot of stuff used to happen at post linking) We also needs much less flags to set up, so it should be even easier to get to work out of the box now The tradeoff in doing so is that now the binary needs at least OSX 10.3.9 to execute To deal with this issue, the JAGUAR flag can be used to compile for older OSes. We will release a binary for old OSes at next release to see if anybody even downloads it (not that many people use OSX 10.2 anymore) GPMI will not work on 10.2 anyway so we will cut support for it some day anyway
2006-02-27(svn r3679) -Fix: [OSX] fixed warning introduced in r3670 about permission ↵bjarni
denied in G5_detector.c when compiling without having Makefile.config
2006-02-25(svn r3675) -Fix: [OSX] made the default gcc names for building universal ↵bjarni
binaries into the newest gcc for each target instead of hardcoding it for 4.0.0
2006-02-25(svn r3674) -Feature: [OSX] Added support for tripple binaries (binaries ↵bjarni
optimised for G3, G5 and i686) G4 have no problems using G3 code while G5 can, but really benefit from getting their own optimised code (Apple: G5 is not just a fast G4) Also changed FAT_BINARY to UNIVERSAL_BINARY since Apple removed most (all?) references to fat binaries on their homepage two days after I added FAT_BINARY
2006-02-25(svn r3673) -Codechange: [OSX] changed the makefile to autodetect if it ↵bjarni
compiles on G5 and then adds flags to optimise for G5 This will not interfere with crosscompiling or universal binaries
2006-01-07(svn r3383) -Code cleanup: [OSX] removed SDL support from FAT binaries as it ↵bjarni
caused problems for non-SDL builds FAT binaries now need to rely on COCOA drivers. SDL didn't work properly anyway
2006-01-07(svn r3382) -Feature: [OSX] added the flag JAGUAR to crosscompile for OSX ↵bjarni
10.2.8 on 10.4
2005-12-10(svn r3286) -Fix: [OSX] 10.2 works again and universal binaries got 10.2 as ↵bjarni
target by default
2005-12-09(svn r3276) reverted the last two commits. OSX 10.2 kept finding new stuff ↵bjarni
to prevent it from running OpenTTD, so now it's not supported anymore
2005-12-09(svn r3275) -Fix: [OSX] removed libpng support and error dialogs from jaguar ↵bjarni
crosscompiles to fix crash
2005-12-09(svn r3274) -Fix: [OSX] added JAGUAR flag to crosscompile for OSX 10.2 ↵bjarni
(codenamed jaguar) JAGUAR and FAT_BINARY can't be used at the same time JAGUAR will disable network support due to missing libs in 10.2
2005-12-09(svn r3273) -Fix: [OSX] PPC part of universal binaries now target 10.3 ↵bjarni
instead of 10.4 10.2 support appears to be broken right now Changed BUILD_UNIVERSAL_BINARY into FAT_BINARY (I got tired of typing)
2005-12-06(svn r3267) -Codechange: [OSX] universal binary makefile code cleanupbjarni
now PPC code is always compiled before x86 code strgen and lng files are only compiled once, which results in shorter building time the makefile now assigns default values to undefined values so much less needs to be set up the code is now easier to maintain