GStreamer multimedia framework
Find a file
Thibault Saunier 1efbb1392d msys2: Fix special lib names regexes and add some necessary ones
And always flush on prints (so we have understandable outputs)
2016-12-13 21:42:01 -03:00
subprojects subprojects: use https:// instead of git:// protocol 2016-11-25 20:06:23 +00:00
.gitignore Add gst-rtsp-server 2016-10-27 00:30:32 +01:00
.gitmodules Remove meson/ submodule 2016-10-20 17:47:07 -03:00
common.py Use mesonintrospect to set library path 2016-12-13 12:58:31 -03:00
git-update git-update: fixes for running on windows 2016-11-17 17:49:17 -03:00
gst-uninstalled.py Add a script to setup a developement environment based on msys2 2016-12-13 14:48:34 -03:00
LICENSE Initial commit 2016-08-25 15:26:28 -03:00
meson.build Work around issue using msys2 provided zlib 2016-12-13 12:58:31 -03:00
meson_options.txt Add gst-rtsp-server 2016-10-27 00:30:32 +01:00
msys2_setup.py msys2: Fix special lib names regexes and add some necessary ones 2016-12-13 21:42:01 -03:00
README.md Add 'update' and git-update targets to update git repos 2016-11-08 15:16:57 -03:00
setup.py Add a script to setup a developement environment based on msys2 2016-12-13 14:48:34 -03:00

gst-build

GStreamer meson based repositories aggregrator

You can build GStreamer and all its modules at once using meson and its subproject feature.

Getting started

Install meson and ninja

You should get meson through your package manager or using:

$ pip3 install --user meson

You should get ninja using your package manager or downloading it from here.

Build GStreamer and its modules

You can get all GStreamer built running:

mkdir build/ && meson build && ninja -C build/

NOTE: on fedora (and maybe other distributions) replace ninja with ninja-build

Development environment

Uninstalled environment

gst-build also contains a special uninstalled target that lets you enter an uninstalled development environment where you will be able to work on GStreamer easily. You can get into that environment running:

ninja -C build/ uninstalled

If your operating system handles symlinks, built modules source code will be available at the root of gst-build/ for example GStreamer core will be in gstreamer/. Otherwise they will be present in subprojects/. You can simply hack in there and to rebuild you just need to rerun ninja -C build/.

Update git subprojects

We added a special update target to update subprojects (it uses git pull --rebase meaning you should always make sure the branches you work on are following the right upstream branch, you can set it with git branch --set-upstream-to origin/master if you are working on gst-build master branch).

Update all GStreamer modules and rebuild:

ninja -C build/ update

Update all GStreamer modules without rebuilding:

ninja -C build/ git-update

Add information about GStreamer development environment in your prompt line

Bash prompt

We automatically handle bash and set $PS1 accordingly

Zsh prompt

In your .zshrc, you should add something like:

export PROMPT="$GST_ENV-$PROMPT"

Using powerline

In your powerline theme configuration file (by default in {POWERLINE INSTALLATION DIR}/config_files/themes/shell/default.json) you should add a new environment segment as follow:

{
  "function": "powerline.segments.common.env.environment",
  "args": { "variable": "GST_ENV" },
  "priority": 50
},