Objective-C

Although both the Mac OS and iOS versions can be included in you application project in the same way and could be used equally from the source code, the installation of the framework and deployment of your application is slightly different. Let's take a look at both versions in the following sections.

MacOS

In the Installation chapter we have seen how to download, unpack the dmg file and install the Sparksee package to get the Sparksee.framework installed in the /Library/Frameworks/ directory. The Mac OS version of the framework is a standard framework containing a dynamic library, so it's installed in a fixed standard location.

To use the Sparksee Objective-C framework in your application, you have to add the Sparksee.framework from /Library/Frameworks/Sparksee.framework to the Link Binary With Libraries build phase of your application project.

Then you can import the header in your source code.

#import <Sparksee/Sparksee.h>

Take into account that your application will depend on the Sparksee dynamic library, therefore the Sparksee framework must be installed on the target computers either manually or redistributed with your own installer.

Alternatively, you could include the framework as a private framework inside your application, but then a modification of the framework library location on the @executable_path instead of the standard /Library/Frameworks/ would be required

iOS

In the Installation chapter we have seen how to download and unpack the dmg file. For iOS, you don't need to install the framework because it would be already there. You can copy it directly to wherever you want because there is not any established standard dynamic library framework.

To use the Sparksee Objective-C framework in your application, you have to add the Sparksee.framework to the Link Binary With Libraries build phase of your application project. You can just drag it there.

Then you can import the header in your source code.

#import <Sparksee/Sparksee.h>

Your iOS application will contain the Sparksee library embedded (it's a static library), so your application deployment should be exactly the same as any other iOS application.

Back to Index