Hello there,
I have researched for a couple of hours now.
About an official confirmation, wether it is legal to run applications
on the devices using a shared library aka. dynamic linked library.
The “iPhone SDK Agreement” is the legal document, which describes the
rules.
The only thing i could find, closing to this matter, is the following part:--------------------------------------------------------------------------
3.3 Program Requirements for Applications
Any Application developed using this SDK must comply with these
criteria and requirements, as they may be modified by Apple form time to
time:
APIs and Functionality:
3.3.1 Applications may only use Published APIs in the manner prescribed
by Apple and must not use or call any unpublished or private APIs
I translate this part to: That it isn’t legally possible to acces API’s
already residing on the iPhone, which is not published by Apple already
(e.g. by dissambling, etc.)
3.3.2 An Application may not itself install or launch other executable
code by any means, including without limitation through the use of a
plugin-in architecture, calling other frameworks, other APIs or
otherwise. No interpreted code may be downloaded and used in an
Application except for code that is interpreted and run by Apple’s
Published APIs and built-in interpreter(s)
I translate this part to: That it isn’t legally possible to make an
application which intepreter(s) scripting languages, or alike … or
launch other executable code by any means …
This doesn’t specifically say anything about shared libraries.
I called the Apple Developer Connection center, and the Apple worker
told me that if the iPhone SDK Agreement, didn’t clearly state that
dynamic linking was against the terms, then he would say it wasn’t.
I suppose that this it the part, which Sam is translating to… making
dynamic linking of the SDL library a no-go?
What do you think?
Kind regards
Mathias Hansen
Sam Lantinga skrev:
What do i have to make sure (SDL License wise), to be able to eventually
distribute my iPhone Application on the App Store.
This is my assumptions:
- I have to link to SDL as a shared object.
- I have to let the user know that i’m using the SDL library.
These are the normal rules for linking under the LGPL.
Unfortunately, the Apple iPhone developer agreement specifically prevents
you from dynamic linking to frameworks and dynamically loading object code.
Thus, as far as I can tell, unless you release the source for your program
there is no way to comply with the LGPL.
However, I am currently in the process of forming a small company to handle
commercial SDL licensing. The license gives you the standard rights to use
the SDL library in your application. The cost covers a single product
across all supported platforms, with discount pricing for multiple products
available.
This license is only available for SDL 1.3 and newer, and all contributors
to the SDL 1.3 code must allow me to redistribute their changes under both
the LGPL and the alternative commercial license.
Please send me private e-mail if you’re interested in pricing and more
information.
See ya!
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment