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.
Multiplatform packaging system
The same system is used to package your application for all platforms
Single-platform packaging system
Your application is packaged using a different system on each 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:
The GStreamer SDK is installed independently of your application, as a prerequisite, in a common place in the target computer (
Private SDK with dynamic linking
Your application deploys the GStreamer SDK to a private folder.
Private SDK with static linking
Your application links statically against the GStreamer SDK, so it effectively becomes part of your application binary.
The following pages give further directions for some of the above options.