The entire point of the deployment target is to allow for you to use a newer SDK (and optionally newer APIs) while targeting an older OS. You won't be able to build on Leopard with SDKs newer than 10.5, but you can run binaries that do.
On Nov 4, 2011, at 7:58 PM, Vojtěch Meluzín wrote: Thanks David, but that won't work on Leopard, or will it? Btw. I found that I can compile 32&64 bit projects on 10.5 SDK, which is quite confusing, but at least here on 10.6.8 both work.
Vojtech
Dne 5. listopadu 2011 3:56 David Duncan <email@hidden> napsal(a):
On Nov 4, 2011, at 2:58 PM, Vojtěch Meluzín wrote: I want my plugins to be 32-bit and 64-bit in one module. So I'm going to use "lipo" to merge the 2 binaries. But the plugin package also contains the resource file created by "rez". That need a parameter "-isysroot /Developer/SDKs/MacOSX10.5.sdk" specified for example. But the 64-bit version must be compiled with SDK 10.6, right? I mean Leopard wasn't 64-bit. And I still want to maintain compatibility with Leopard for 32-bit version, so I need to 10.5 SDK, so how to do that?? Or can I use 10.5 for both cases?
Unless you are trying to target 64-bit PowerPC, you don't need the 10.5 SDK, just use the 10.6 SDK and set the deployment target for 10.5. -- Reality is what, when you stop believing in it, doesn't go away. Failure is not an option. It is a privilege reserved for those who try.
David Duncan
--
Reality is what, when you stop believing in it, doesn't go away.
Failure is not an option. It is a privilege reserved for those who try.
David Duncan
|