Eric Hoch wrote:
I don't know if it's possible to build on Tiger but switching to
Leopard solves this problem but causes others like having binaries
which only run on Leopard :-) I experienced this after my first
Leopard build couldn't be installed on a friends Tiger machine.
Since we provide Aqua OOo for Tiger and Leopard you may need two
build environments or we need four versions of OOo. But this should
be discussed in a Mac Porters meeting or in a seperate thread.
There are ways of compiling on Leopard that will also run on Tiger (or
even Panther). You can do this from the command line, too, with the
proper options:
SDK=/Developer/SDKs/MacOSX10.4.0.sdk
CFLAGS= -isysroot ${SDK}
LDFLAGS= -isysroot ${SDK} -Wl,-syslibroot,${SDK}
ENVP= MACOSX_DEPLOYMENT_TARGET=10.3
The above should build something that should run on Panther through
Leopard, but only features of Tiger would be available on Tiger &
Leopard. Using the 10.5 SDK and a deployment target of 10.4 should allow
the code to run on Tiger and Leopard, and you should have Leopard
features available on Leopard. (You'll need to test for these at runtime.)
Options are available for universal binaries as well. You basically add
_ppc or _i386 after the variables for each CPU. However, that would
nearly double the size of the OO.o installation, and it is pretty darned
big as it is.
The above information comes from the Apple Cross Development Programming
Guide:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/Introduction/chapter_1_section_1.html
Cheers,
Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
