gstreamer/Deploying+your+application.markdown

Deploying your application

This page last changed on Jun 12, 2013 by xartigas.

Once the development of your application is finished, you will need to deploy it to the target machine, usually in the form of a package or 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

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 to use a different packaging system for each platform, or use one that can deliver to all platforms simultaneously. This table summarizes the pros and cons of each option.

	Pros	Cons
Multiplatform packaging system  The same system is used to package your application for all platforms	You only need to develop your packaging system once, and it works for all supported platforms.	On some platforms, the packaging system might impose artificial restrictions inherited from the other platforms.
Single-platform packaging system Your application is packaged using a different system on each platform.	You can make use of all the advantages each packaging system can offer.	You need to develop a new packaging system for each supported platform.

The GStreamer SDK itself supports three different platforms (Linux, Mac OS X and Windows) 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

You can install the GStreamer SDK 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:

	Pros	Cons
Shared SDK The GStreamer SDK is installed independently of your application, as a prerequisite, in a common place in the target computer (C:\Program Files, for example). You application uses an environment variable to locate it.	If more than one application in the target computer uses the SDK, it is installed only once and shared, reducing disk usage.	Tampering or corruption of the shared SDK installation can make your application fail. The SDK libraries are unprotected and open to tampering.
Private SDK with dynamic linking Your application deploys the GStreamer SDK to a private folder.	Your SDK is independent of other applications, so it does not get corrupted if other applications mess with their installations.	If multiple applications in the target computer use the GStreamer SDK, it won’t be shared, consuming more disk space. The SDK libraries are unprotected and open to tampering.
Private SDK with static linking Your application links statically against the GStreamer SDK, so it effectively becomes part of your application binary.	Your SDK is independent of other applications, so it does not get corrupted if other applications mess with their installations. It is much harder to tamper with the SDK, since it is embedded in your application.	If multiple applications in the target computer use the GStreamer SDK, it won’t be shared, consuming more disk space.

The following pages give further directions for some of the above options.

• Platform-specific packaging methods:
  • For Mac OS X
  • For Windows
• Multiplatform deployment using Cerbero

 

Document generated by Confluence on Oct 08, 2015 10:27