Re: Leopard-specific functionality in non–L eopard-only project

2008-06-21 Thread Mike Abdullah
If you're desperate to stick with the 10.4 SDK, I'd suggest the best approach is just to create your own header that mimics the method. So you'd end up with something like: @interface NSWindow (LeopardOnlyMethods) - (void)setCollectionBehavior:(int)behavior; @end ... [window setCollectionBeh

Re: Leopard-specific functionality in non–L eopard-only project

2008-06-21 Thread Mark Munz
If you're sharing the project between developers, they both need to be using the same SDK (ie. 10.5 in this example). The end product will run on both 10.4 and 10.5, but the development has to be done on a 10.5 machine (you can't develop for future OS's from an older OS). Another option (for someo

Re: Leopard-specific functionality in non–L eopard-only project

2008-06-21 Thread Jacob
Alright, thanks, but will that work if someone tries to use the project for development who's not on 10.5? On Sat, Jun 21, 2008 at 1:01 PM, Mark Munz <[EMAIL PROTECTED]> wrote: > The trick is to set the SDK to 10.5 and then in the target build settings, > set: > > Mac OS X Deployment Target to M

Re: Leopard-specific functionality in non–L eopard-only project

2008-06-21 Thread Mark Munz
The trick is to set the SDK to 10.5 and then in the target build settings, set: Mac OS X Deployment Target to Mac OS X 10.4. (under Deployment) You'll want to set it for all your configurations: (Debug, Release, etc) On Sat, Jun 21, 2008 at 12:51 PM, Jacob Bandes-Storch <[EMAIL PROTECTED]> wrote