Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
an Xcode project to create a monolithic framework from an existing FFmpeg installation
C C++
Branch: master

Sync with current MacPorts' FFmpeg (2.1.4, libavutil 52. 48.101 / 52.…

… 48.101

  libavcodec     55. 39.101 / 55. 39.101
  libavformat    55. 19.104 / 55. 19.104
  libavdevice    55.  5.100 / 55.  5.100
  libavfilter     3. 90.100 /  3. 90.100
  libavresample   1.  1.  0 /  1.  1.  0
  libswscale      2.  5.101 /  2.  5.101
  libswresample   0. 17.104 /  0. 17.104
  libpostproc    52.  3.100 / 52.  3.100)
latest commit e56a39c50a
@RJVB authored

README.txt

This is an Xcode project file that allows to create a standalone, monolithic framework from the static libraries of an existing FFmpeg installation. It is configured to expect the +nonfree+universal variant of the MacPorts repository, installed in (accessible through) that project's default installation directory, /opt/local .

The central build target is FFmpegFW-mp (mp standing for MacPorts).

The build procedure is as follows
- a script catches the initial list of files to be linked. It then retrieves the various FFmpeg static libraries, extracting the i386 and x86_64 archives. Duplicate entries for log2_tab.o are deleted where relevant. A new master link object file is then created from the libraries, using ld -r -all_load , and the original LinkFileList replaced by one containing that master object, plus any objects mentioned originally but not yet present on disk.
- Another script copies the header files from the MacPorts tree into the framework bundle.
- During the final link step, Xcode links in the various libraries required, and generates a framework.

An attempt is made to reduce dependencies on MacPorts as much as possible, by pulling in the static versions of libraries on which the FFmpeg libs depend. The remaining shared libraries are linked weakly, meaning their absence is of no incidence until their functionality is called upon. That’s of especial interest for libSDL, which is used by ffplay, but probably unlikely so by any other projects.

The project is set up to be placed in a subdirectory of the FFmpeg source repository as can be downloaded via git, but the source files are only used for reference, EXCEPT FOR the License file. Its absence should not be a problem.
It is possible to modify the initial script to use self-compiled libraries, extracting the install location from the build files. In that case you will have to check to make sure the correct external libraries are linked. NB: when adding libraries to a target’s dependencies, Xcode will add the location to the library search path; it will not remove those entries when the corresponding libraries are removed!
Something went wrong with that request. Please try again.