GStreamer multimedia framework
Go to file
2016-11-08 15:10:50 -03:00
subprojects Add gst-rtsp-server 2016-10-27 00:30:32 +01: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 Minor improvement in the git function 2016-10-11 02:05:39 +02:00
git-update git-update: Also update gst-build 2016-11-08 15:10:50 -03:00
gst-uninstalled.py Properly setup environment for python development if gst-python is being built 2016-11-04 12:30:28 -03:00
LICENSE Initial commit 2016-08-25 15:26:28 -03:00
meson.build Include libav dependency in FFmpeg check 2016-11-03 21:51:01 -03:00
meson_options.txt Add gst-rtsp-server 2016-10-27 00:30:32 +01:00
README.md Fix setting $PS1 for bash 2016-11-02 16:20:56 -03:00
setup Get absolute path to run meson 2016-10-26 19:46:09 -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

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/.

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
},