diff options
Diffstat (limited to 'sdk-deploying-your-application.md')
| -rw-r--r-- | sdk-deploying-your-application.md | 62 |
1 files changed, 30 insertions, 32 deletions
diff --git a/sdk-deploying-your-application.md b/sdk-deploying-your-application.md index 5100554..b39b3b8 100644 --- a/sdk-deploying-your-application.md +++ b/sdk-deploying-your-application.md @@ -1,5 +1,5 @@ --- -short-description: Deploy the SDK with your application +short-description: Deploy GStreamer with your application ... # Deploying your application @@ -10,7 +10,7 @@ installer. You have several options here, and, even though this subject is not really in the scope of this documentation, we will give some hints to try to help you. -# Multiplatform vs. single-platform packaging system +## Multiplatform vs. single-platform packaging system The first choice you need to make is whether you want to deploy your application to more than one platform. If yes, then you have the choice @@ -33,8 +33,8 @@ pros and cons of each option. </thead> <tbody> <tr class="odd"> -<td><p><strong><span style="color: rgb(0,0,0);">Multiplatform packaging </span></strong><span style="color: rgb(0,0,0);"><strong>system</strong></span></p> -<p><span style="color: rgb(0,0,0);"> </span>The same system is used to package your application for all platforms</p></td> +<td><p><strong>Multiplatform packaging system</strong></p> +<p>The same system is used to package your application for all platforms</p></td> <td><ul> <li><p>You only need to develop your packaging system once, and it works for all supported platforms.</p></li> </ul></td> @@ -46,24 +46,24 @@ pros and cons of each option. <td><p><strong>Single-platform packaging system</strong></p> <p>Your application is packaged using a different system on each platform.</p></td> <td><ul> -<li><p>You can make use of all the advantages each <span>packaging </span>system can offer.</p> -<p> </p></li> +<li><p>You can make use of all the advantages each packaging system can offer.</p> +</li> </ul></td> <td><ul> -<li><p>You need to develop a new <span>packaging </span>system for each supported platform.</p></li> +<li><p>You need to develop a new packaging system for each supported platform.</p></li> </ul></td> </tr> </tbody> </table> -The GStreamer SDK itself supports three different platforms (Linux, Mac -OS X and Windows) and has been built using a multiplatform packaging +GStreamer itself supports many different platforms (Linux, iOS, Android, Mac +OS X, Windows, etc) and has been built using a multiplatform packaging system named **Cerbero**, which is available for you to use, should you choose to go down this route. -# Shared vs. private GStreamer deployment +## Shared vs. private GStreamer deployment -You can install the GStreamer SDK in the target machine in the same way +You can install GStreamer in the target machine in the same way you installed it in your development machine, you can deploy it privately, or you can even customize it before deploying. Here you have a few options: @@ -76,43 +76,43 @@ a few options: </colgroup> <thead> <tr class="header"> -<th> </th> +<th></th> <th>Pros</th> <th>Cons</th> </tr> </thead> <tbody> <tr class="odd"> -<td><p><strong>Shared SDK</strong></p> -<p>The GStreamer SDK is installed independently of your application, as a prerequisite, in a common place in the target computer (<code>C:\Program Files</code>, for example). You application uses an environment variable to locate it.</p></td> +<td><p><strong>Shared GStreamer</strong></p> +<p>GStreamer is installed independently of your application, as a prerequisite, in a common place in the target computer (<code>C:\Program Files</code>, for example). You application uses an environment variable to locate it.</p></td> <td><ul> -<li><p>If more than one application in the target computer uses the SDK, it is installed only once and shared, reducing disk usage.</p></li> +<li>If more than one application in the target computer uses GStreamer, it is installed only once and shared, reducing disk usage.</li> </ul></td> <td><ul> -<li>Tampering or corruption of the shared SDK installation can make your application fail.</li> -<li><p>The SDK libraries are unprotected and open to tampering.</p></li> +<li>Tampering or corruption of the shared GStreamer installation can make your application fail.</li> </ul></td> </tr> <tr class="even"> -<td><p><strong>Private SDK with dynamic linking</strong></p> -<p>Your application deploys the GStreamer SDK to a private folder.</p></td> +<td><p><strong>Private GStreamer with dynamic linking</strong></p> +<p>Your application deploys GStreamer to a private folder.</p></td> <td><ul> -<li><p>Your SDK is independent of other applications, so it does not get corrupted if other applications mess with their installations.</p></li> +<li>Your GStreamer is independent of other applications, so it does not get corrupted if other applications mess with their installations.</li> </ul></td> <td><ul> -<li><p>If multiple applications in the target computer use the GStreamer SDK, it won’t be shared, consuming more disk space.</p></li> -<li><p>The SDK libraries are unprotected and open to tampering.</p></li> +<li>If multiple applications in the target computer use GStreamer, it won’t be shared, consuming more disk space.</li> </ul></td> </tr> <tr class="odd"> -<td><p><strong>Private SDK with static linking</strong></p> -<p>Your application links statically against the GStreamer SDK, so it effectively becomes part of your application binary.</p></td> +<td><p><strong>Private GStreamer with static linking</strong></p> +<p>Your application links statically against GStreamer, so it effectively becomes part of your application binary.</p></td> <td><ul> -<li>Your SDK is independent of other applications, so it does not get corrupted if other applications mess with their installations.</li> -<li>It is much harder to tamper with the SDK, since it is embedded in your application.</li> +<li>Your GStreamer is independent of other applications, so it does not get corrupted if other applications mess with their installations.</li> +<li>Deployment for ordinary users is easier as you have fewer files.</li> +<li>This is your only choice on iOS.</li> </ul></td> <td><ul> -<li><span>If multiple applications in the target computer use the GStreamer SDK, it won’t be shared, consuming more disk space.</span></li> +<li>If multiple applications in the target computer use GStreamer, it won’t be shared, consuming more disk space.</li> +<li>You need to provide the required files for your users to re-link your application against a modified GStreamer as required by the license.</li> </ul></td> </tr> </tbody> @@ -122,9 +122,7 @@ The following pages give further directions for some of the above options. - Platform-specific packaging methods: - - For [Mac OS X](Mac%2BOS%2BX%2Bdeployment.html) - - For [Windows](Windows%2Bdeployment.html) + - For [Mac OS X](sdk-mac-osx-deployment.md) + - For [Windows](sdk-windows-deployment.md) - [Multiplatform deployment using - Cerbero](Multiplatform%2Bdeployment%2Busing%2BCerbero.html) - - + Cerbero](sdk-multiplatform-deployment-using-cerbero.md) |