Currently, the most convenient way to generate GStreamer binaries for Mac is to use the MacPorts build system. It automatically handles dependencies and patches, and it is kept well up-to-date. However, the main disadvantage of MacPorts is that the resulting GStreamer libraries are meant to be placed inside a specific location in the disk, usually /opt/local, which makes difficult to bundle them into 3rd party applications and also requires separate installs to deploy GStreamer on the end user’s machine. The reason for this problem is that the compilation process in MacPorts hard-codes the absolute paths of the dependencies into the binaries and/or libraries. The methods and scripts described below allow one to modify the GStreamer binaries built with MacPorts so they contain only relative references to dependencies, thus facilitating the integration of GStreamer with 3rd party applications on Mac OSX. These scripts and accompanying documentation are already part of the OSSBuild distribution.
Read the rest of this entry »
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
- Privacy
codeanticode 