libspotify-mac 12.1.51.2

libspotify-mac 12.1.51.2

TestsTested
LangLanguage Obj-CObjective C
License Commercial
ReleasedLast Release Dec 2014

Maintained by Unclaimed.



libspotify-mac 12.1.51.2

  • By
  • Spotify AB
                             libspotify 12.1.51
               ----------------------------------------

                   Copyright © 2006-2012 Spotify Ltd
  1. INTRODUCTION

    This is the libspotify C API package. With it, you can write applications that utilize the Spotify music streaming service.

  2. PACKAGE STRUCTURE

    The package is structured as follows:

    libspotify-12.1.51-Darwin/ ChangeLog Contains description of new and changed functionality in libspotify README This README file LICENSE License governing the library, and associated files. licenses.xhtml License governing third party libraries included in libspotify. libspotify.framework The libspotify framework, including the header and shared library. doc/ html/ Documentation in HTML format This information is also available online. images/ Graphics for use with applications using libspotify. See section 6 below. man3/ Manual pages for libspotify examples/ Root directory for the example source code

  3. COMPATIBILITY AND REQUIREMENTS

    The library was compiled as a two-way universal binary on Mac OS X 10.6. It requires:

    • an Intel processor
    • Mac OS X 10.4 or later
  4. INSTALLATION

4.1 Bundling in applications and plugins

libspotify.framework is built with an install_name of
@loader_path/../Frameworks/libspotify.framework/Versions/Current/libspotify,
and should work as-is when bundled with your application or plugin.

To bundle it using Xcode 4:
1. Drag and drop libspotify.framework to the "Frameworks" group in
   the project navigator. Check "Copy items into destination groups's
   folder (if needed)".
2. In the project navigator, select your project. Select your target
   and select the "Build Phases" tab.
3. Click on "Add Build Phase->Add Copy files".
4. Select Destination "Frameworks" in the "Copy Files" group.
5. You probably want to rename this build phase by double clicking on
   the title. Name it something like "Copy Frameworks".
6. Drag libspotify.framework from the project navigator and drop it
   in the "Copy Frameworks" group.
7. Build. You can confirm that the above worked by right-clicking
   on your .app under Products in the project navigator and and selecting
   "Show in Finder" in the menu. Right-click on the application bundle and
   choose "Show Package Contents". Verify that have a
   Contents/Frameworks/libspotify.framework folder in there.

4.2 Building command line applications

Since libspotify.framework is built with an install_name appropriate
for bundling with apps, it will be tedious to use with command line
utilities by default. The recommended procedure in this situation
is to install libspotify.framework into /Library/Frameworks, and then use
install_name_tool to rewrite the install_name to that path in your
executable. The examples show how to do this, but in essence:
    install_name_tool -change \     
        @loader_path/../Frameworks/libspotify.framework/libspotify \    
        /Library/Frameworks/libspotify.framework/libspotify \
        path_to_executable

If you'd like to bundle the framework with your executable some other
way, switch /Library/Frameworks in the above command to something else,
possibly relative to @loader_path (which is the path to your executable
at runtime).

4.3 Examples There are a number of examples in doc/examples that will act as great starting points. Have fun!

  1. APPLICATION KEYS

    The example programs require a file called appkey.c which is not present in the package. You will need to request an application key at the developer website at http://developer.spotify.com/ before being able to run them.

  2. LOGOTYPES AND TRADEMARK

    The graphics found in the images/ subdirectory are available for use in applications using libspotify. The terms and conditions for the use of these are available on http://developer.spotify.com/.

    A text file is included in images/, containing the text to be used in non-graphical applications.

  3. LICENSE

    You should have received a separate LICENSE file together with this README.