Re: Building For Different Macintosh OS
Re: Building For Different Macintosh OS
- Subject: Re: Building For Different Macintosh OS
- From: Christiaan Hofman <email@hidden>
- Date: Thu, 1 Jul 2010 22:53:06 +0200
On Jul 1, 2010, at 19:51, Kevin Walker wrote:
> I am facing a task which requires building against different versions of similar source files to account for changes in an Apple provided framework between OS X 10.4 and OS X 10.6. I would prefer to have a runtime switch that uses the correct version of the calls and supporting classes (CoreAudio support in this case) depending upon which OS version is being used but I am not forced to go this route if another type of solution looks better.
>
> Currently I am considering moving a majority of my code into a framework stored in the application bundle and taking the code that depends upon the changing support classes mentioned above and moving it into dylibs. There would be a dylib for each OS type I am concerned about and the right dylib would be loaded manually at runtime and the required functions then accessed by symbol lookups. The framework mentioned above should permit the remaining application code and the dylib code to access the same supporting code if I understand things properly.
>
> I anyone has any suggestions about this or different approaches to this issue, I welcome any advice you can provide.
>
> The reason I am posing this question to the Xcode Users list is this appear to be more of a project organization and targets issues overall.
>
>
> Thanks,
>
> Kevin (KJ) Walker
> Senior Mac Developer
> SmartSound Software, Inc.
>
A similar approach that may be more standard here is to have loadable bundles containing the different codes. This is because it's easy in Cocoa to load bundles.
Christiaan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden