Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
docs/ | 12-May-2024 | - | 31,360 | 27,916 | ||
ext/ | 12-May-2024 | - | 65,367 | 47,321 | ||
gst/ | 12-May-2024 | - | 129,617 | 95,136 | ||
gst-libs/ | 12-May-2024 | - | 320,721 | 222,069 | ||
po/ | 12-May-2024 | - | 33,488 | 23,698 | ||
scripts/ | 12-May-2024 | - | 200 | 75 | ||
sys/ | 12-May-2024 | - | 7,986 | 5,457 | ||
tests/ | 12-May-2024 | - | 102,472 | 74,699 | ||
tools/ | 12-May-2024 | - | 3,480 | 2,748 | ||
AUTHORS | D | 12-May-2024 | 977 | 24 | 23 | |
BUILD.gn | D | 12-May-2024 | 15.3 KiB | 598 | 522 | |
COPYING | D | 12-May-2024 | 25.8 KiB | 504 | 418 | |
ChangeLog | D | 12-May-2024 | 5.8 MiB | 155,749 | 121,438 | |
MAINTAINERS | D | 12-May-2024 | 384 | 13 | 9 | |
NEWS | D | 12-May-2024 | 107.9 KiB | 2,526 | 1,998 | |
README.md | D | 12-May-2024 | 7.4 KiB | 197 | 138 | |
README.static-linking | D | 12-May-2024 | 7.6 KiB | 175 | 136 | |
RELEASE | D | 12-May-2024 | 3.7 KiB | 101 | 63 | |
REQUIREMENTS | D | 12-May-2024 | 2.5 KiB | 100 | 77 | |
config.h | D | 12-May-2024 | 2.1 KiB | 136 | 73 | |
gst-plugins-base.doap | D | 12-May-2024 | 34.5 KiB | 1,134 | 1,023 | |
meson.build | D | 12-May-2024 | 18.5 KiB | 552 | 482 | |
meson_options.txt | D | 12-May-2024 | 6.2 KiB | 91 | 84 |
README.md
1GStreamer 1.20.x stable series 2 3WHAT IT IS 4---------- 5 6This is GStreamer, a framework for streaming media. 7 8WHERE TO START 9-------------- 10 11We have a website at 12 13 https://gstreamer.freedesktop.org 14 15Our documentation, including tutorials, API reference and FAQ can be found at 16 17 https://gstreamer.freedesktop.org/documentation/ 18 19You can subscribe to our mailing lists: 20 21 https://lists.freedesktop.org/mailman/listinfo/gstreamer-announce 22 23 https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel 24 25We track bugs, feature requests and merge requests (patches) in GitLab at 26 27 https://gitlab.freedesktop.org/gstreamer/ 28 29You can join us on IRC - #gstreamer on irc.oftc.net 30 31GStreamer 1.0 series 32-------------------- 33 34Starring 35 36 GSTREAMER 37 38The core around which all other modules revolve. Base functionality and 39libraries, some essential elements, documentation, and testing. 40 41 BASE 42 43A well-groomed and well-maintained collection of GStreamer plug-ins and 44elements, spanning the range of possible types of elements one would want 45to write for GStreamer. 46 47And introducing, for the first time ever, on the development screen ... 48 49 THE GOOD 50 51 --- "Such ingratitude. After all the times I've saved your life." 52 53A collection of plug-ins you'd want to have right next to you on the 54battlefield. Shooting sharp and making no mistakes, these plug-ins have it 55all: good looks, good code, and good licensing. Documented and dressed up 56in tests. If you're looking for a role model to base your own plug-in on, 57here it is. 58 59If you find a plot hole or a badly lip-synced line of code in them, 60let us know - it is a matter of honour for us to ensure Blondie doesn't look 61like he's been walking 100 miles through the desert without water. 62 63 THE UGLY 64 65 --- "When you have to shoot, shoot. Don't talk." 66 67There are times when the world needs a color between black and white. 68Quality code to match the good's, but two-timing, backstabbing and ready to 69sell your freedom down the river. These plug-ins might have a patent noose 70around their neck, or a lock-up license, or any other problem that makes you 71think twice about shipping them. 72 73We don't call them ugly because we like them less. Does a mother love her 74son less because he's not as pretty as the other ones ? No - she commends 75him on his great personality. These plug-ins are the life of the party. 76And we'll still step in and set them straight if you report any unacceptable 77behaviour - because there are two kinds of people in the world, my friend: 78those with a rope around their neck and the people who do the cutting. 79 80 THE BAD 81 82 --- "That an accusation?" 83 84No perfectly groomed moustache or any amount of fine clothing is going to 85cover up the truth - these plug-ins are Bad with a capital B. 86They look fine on the outside, and might even appear to get the job done, but 87at the end of the day they're a black sheep. Without a golden-haired angel 88to watch over them, they'll probably land in an unmarked grave at the final 89showdown. 90 91Don't bug us about their quality - exercise your Free Software rights, 92patch up the offender and send us the patch on the fastest steed you can 93steal from the Confederates. Because you see, in this world, there's two 94kinds of people, my friend: those with loaded guns and those who dig. 95You dig. 96 97The Lowdown 98----------- 99 100 --- "I've never seen so many plug-ins wasted so badly." 101 102GStreamer Plug-ins has grown so big that it's hard to separate the wheat from 103the chaff. Also, distributors have brought up issues about the legal status 104of some of the plug-ins we ship. To remedy this, we've divided the previous 105set of available plug-ins into four modules: 106 107- gst-plugins-base: a small and fixed set of plug-ins, covering a wide range 108 of possible types of elements; these are continuously kept up-to-date 109 with any core changes during the development series. 110 111 - We believe distributors can safely ship these plug-ins. 112 - People writing elements should base their code on these elements. 113 - These elements come with examples, documentation, and regression tests. 114 115- gst-plugins-good: a set of plug-ins that we consider to have good quality 116 code, correct functionality, our preferred license (LGPL for the plug-in 117 code, LGPL or LGPL-compatible for the supporting library). 118 119 - We believe distributors can safely ship these plug-ins. 120 - People writing elements should base their code on these elements. 121 122- gst-plugins-ugly: a set of plug-ins that have good quality and correct 123 functionality, but distributing them might pose problems. The license 124 on either the plug-ins or the supporting libraries might not be how we'd 125 like. The code might be widely known to present patent problems. 126 127 - Distributors should check if they want/can ship these plug-ins. 128 - People writing elements should base their code on these elements. 129 130- gst-plugins-bad: a set of plug-ins that aren't up to par compared to the 131 rest. They might be close to being good quality, but they're missing 132 something - be it a good code review, some documentation, a set of tests, 133 a real live maintainer, or some actual wide use. 134 If the blanks are filled in they might be upgraded to become part of 135 either gst-plugins-good or gst-plugins-ugly, depending on the other factors. 136 137 - If the plug-ins break, you can't complain - instead, you can fix the 138 problem and send us a patch, or bribe someone into fixing them for you. 139 - New contributors can start here for things to work on. 140 141PLATFORMS 142--------- 143 144- Linux is of course fully supported 145- FreeBSD is reported to work; other BSDs should work too; same for Solaris 146- MacOS works, binary 1.x packages can be built using the cerbero build tool 147- Windows works; binary 1.x packages can be built using the cerbero build tool 148 - MSys/MinGW builds 149 - Microsoft Visual Studio builds are also available and supported 150- Android works, binary 1.x packages can be built using the cerbero build tool 151- iOS works 152 153INSTALLING FROM PACKAGES 154------------------------ 155 156You should always prefer installing from packages first. GStreamer is 157well-maintained for a number of distributions, including Fedora, Debian, 158Ubuntu, Mandrake, Arch Linux, Gentoo, ... 159 160Only in cases where you: 161 162 - want to hack on GStreamer 163 - want to verify that a bug has been fixed 164 - do not have a sane distribution 165 166should you choose to build from source tarballs or git. 167 168Find more information about the various packages at 169 170 https://gstreamer.freedesktop.org/download/ 171 172For in-depth instructions about building GStreamer visit: 173[getting-started](https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/main/README.md#getting-started). 174 175PLUG-IN DEPENDENCIES AND LICENSES 176--------------------------------- 177 178GStreamer is developed under the terms of the LGPL (see COPYING file for 179details). Some of our plug-ins however rely on libraries which are available 180under other licenses. This means that if you are distributing an application 181which has a non-GPL compatible license (for instance a closed-source 182application) with GStreamer, you have to make sure not to distribute GPL-linked 183plug-ins. 184 185When using GPL-linked plug-ins, GStreamer is for all practical reasons 186under the GPL itself. 187 188HISTORY 189------- 190 191The fundamental design comes from the video pipeline at Oregon Graduate 192Institute, as well as some ideas from DirectMedia. It's based on plug-ins that 193will provide the various codec and other functionality. The interface 194hopefully is generic enough for various companies (ahem, Apple) to release 195binary codecs for Linux, until such time as they get a clue and release the 196source. 197
README.static-linking
1================================= 2 GStreamer Static Linking README 3================================= 4 5DRAFT, April 2013 6 7 8 I. INTRODUCTION 9 10It is possible to link GStreamer libraries, plugins and applications 11statically, both in case of free/libre/open-source software applications 12and proprietary applications. On some platforms static linking may even 13be required. 14 15However, distributing statically linked binaries using GStreamer usually 16requires additional effort to stay compliant with the GNU LGPL v2.1 license. 17 18The purpose of this document is to draw attention to this fact, and to 19summarise in layman's terms what we believe is required from anyone 20distributing statically linked GStreamer binaries. Most of this also 21applies to dynamically linked GStreamer binaries. 22 23 24 II. DISCLAIMER 25 26This document is not legal advice, nor is it comprehensive. It may use 27words in ways that do not match the definition or use in the license 28text. It may even be outright wrong. Read the license text for all the 29details, it is the only legally binding document in this respect. 30 31This document is primarily concerned with the implications for the 32distribution of binaries based on LGPL-licensed software as imposed by 33the LGPL license, but there may be other restrictions to the distribution 34of such binaries, such as terms and conditions of distribution channels 35(e.g. "app stores"). 36 37 38 III. THE SPIRIT OF THE LGPL LICENSE 39 40The GNU LGPL v2.1 license allows use of such-licensed software by 41proprietary applications, but still aims to ensure that at least the 42LGPL-licensed software parts remain free under all circumstances. This 43means any changes to LGPL-licensed source code must be documented and 44be made available on request to those who received binaries of the 45software. It also means that it must be possible to make changes to the 46LGPL-licensed software parts and make the application use those, as far 47as that is possible. And that recipients of an application using 48LGPL-licensed software are made aware of their rights according to the 49LGPL license. 50 51In an environment where GStreamer libraries and plugins are used as 52dynamically-loaded shared objects (DLL/.so/.dyn files), this is usually 53not a big problem, because it is fairly easy to compile a modified version 54of the GStreamer libraries or LGPL plugins, and the application will/should 55just pick up and use the modified version automatically. All that is needed 56is for the original, LGPL-licensed source code and source code modifications 57to be made available, and for a way to build the libraries or plugins for 58the platform required (usually that will be using the build system scripts 59that come with GStreamer, and using the typical build environment on the 60system in question, but where that is not the case the needed build scripts 61and/or tools would need to be provided as well). 62 63 64 IV. THINGS YOU NEED TO DO 65 66 * You must tell users of your application that you are using LGPL-licensed 67 software, which LGPL-licensed software exactly, and you must provide them 68 with a copy of the license so they know their rights under the LGPL. 69 70 * You must provide (on request) all the source code and all the changes 71 or additions you have made to the LGPL-licensed software you are using. 72 73 For GStreamer code we would recommend that the changes be provided either 74 in form of a branch in a git repository, or as a set of "git format-patch"- 75 style patches against a GStreamer release or a snapshot of a GStreamer git 76 repository. The patches should ideally say what was changed and why it 77 was changed, and there should ideally be separate patches for independent 78 changes. 79 80 * You must provide a way for users of your application to make changes to 81 the LGPL-licensed parts of the code, and re-create a full application 82 binary with the changes (using the standard toolchain and tools of the 83 target platform; if you are using a custom toolchain or custom tools 84 you must provide these and document how to use them to create a new 85 application binary). 86 87 Note that this of course does not mean that the user is allowed to 88 re-distribute the changed application. Nor does it mean that you have 89 to provide your proprietary source code - it is sufficient to provide a 90 ready-made compiled object file that can be relinked into an application 91 binary with the re-compiled LGPL components. 92 93 94 V. THINGS TO LOOK OUT FOR 95 96While most GStreamer plugins and the libraries they depend on are licensed 97under the LGPL or even more permissive licenses, that is not the case for 98all plugins and libraries used, esp. those in the gst-plugins-ugly or 99some of those in the gst-plugins-bad set of plugins. 100 101When statically linking proprietary code, care must be taken not to 102statically link plugins or libraries that are licensed under less permissive 103terms than the LGPL, such as e.g. GPL-licensed libraries. 104 105 106 VI. SPECIAL CONSIDERATIONS FOR SPECIFIC USE-CASES 107 108 109 1. Proprietary GStreamer/GLib-based Application On iOS 110 111Let's assume an individual or a company wants to distribute a proprietary 112iOS application that is built on top of GStreamer and GLib through 113Apple's App Store. At the time of writing the Apple iPhone developer 114agreement didn’t allow the bundling of shared libraries, so distributing 115a proprietary iOS application with shared libraries is only possible using 116distribution mechanisms outside of the App Store and/or only to jailbroken 117devices, a prospect that may not appeal to our individual or company. So the 118only alternative then is to link everything statically, which means the 119obligations mentioned above come into play. 120 121 122 2. Example: Jabber on iOS 123 124Tandberg (now Cisco) created a Jabber application for iOS, based on GStreamer. 125On request they provided an LGPL compliance bundle in form of a zip file, with 126roughly the following contents: 127 128buildapp.sh 129readme.txt 130Jabber/Jabber-Info.plist 131Jabber/libip.a [236MB binary with proprietary code] 132Jabber/main.mm 133Jabber/xcconfig/Application.xcconfig 134Jabber/xcconfig/Debug.xcconfig 135Jabber/xcconfig/Release.xcconfig 136Jabber/xcconfig/Shared.xcconfig 137Jabber/Resources/*.lproj/Localizable.strings 138Jabber/Resources/{Images,Audio,Sounds,IB,Message Styles,Emoticons,Fonts}/* 139Jabber/Resources/* 140Jabber.xcodeproj/project.pbxproj 141Jabber.xcodeproj/project.xcworkspace/contents.xcworkspacedata 142opensource/build/config.site 143opensource/build/m4/movi.m4 144opensource/build/scripts/clean-deps.sh 145opensource/build/scripts/fixup-makefile.sh 146opensource/build/scripts/MoviMaker.py 147opensource/build.sh 148opensource/env.sh 149opensource/Makefile 150opensource/external/glib/* 151opensource/external/gstreamer/{gstreamer,gst-plugins-*}/* 152opensource/external/openssl/* 153opensource/external/proxy-libintl/* 154opensource/toolchain/darwin-x86/bin/{misc autotoools,m4,glib-mkenums,glib-genmarshal,libtool,pkg-config,etc.} 155opensource/toolchain/darwin-x86/share/{aclocal,aclocal-1.11,autoconf,automake-1.11,libtool}/* 156opensource/toolchain/darwin-x86/share/Config.pm 157opensource/toolchain/darwin-x86/share/Config.pm.movi.in 158patches/glib/glib.patch 159patches/gst-plugins-bad/gst-plugins-bad.patch 160patches/gst-plugins-base/gst-plugins-base.patch 161patches/gst-plugins-good/gst-plugins-good.patch 162patches/gstreamer/gstreamer.patch 163patches/openssl/openssl.patch 164 165readme.txt starts with "This Readme file describes how to build the Cisco 166Jabber for iPad application. You need to install Xcode, but the final package 167is built by running buildapp.sh." and describes how to build project, 168prerequisites, the procedure in detail, and a "How to Include Provisioning 169Profile Manually / Alternate Code Signing Instructions" section. 170 171 172 3. Random Links Which May Be Of Interest 173 174[0] http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/ 175