3 GStreamer [meson](http://mesonbuild.com/) based repositories aggregrator
5 You can build GStreamer and all its modules at once using
6 meson and its [subproject](https://github.com/mesonbuild/meson/wiki/Subprojects) feature.
10 ### Install meson and ninja
12 You should get meson through your package manager or using:
14 $ pip3 install --user meson
16 You should get `ninja` using your package manager or downloading it from
17 [here](https://github.com/ninja-build/ninja/releases).
19 ### Build GStreamer and its modules
21 You can get all GStreamer built running:
24 mkdir build/ && meson build && ninja -C build/
27 NOTE: on fedora (and maybe other distributions) replace `ninja` with `ninja-build`
29 # Development environment
31 ## Uninstalled environment
33 gst-build also contains a special `uninstalled` target that lets you enter an
34 uninstalled development environment where you will be able to work on GStreamer
35 easily. You can get into that environment running:
38 ninja -C build/ uninstalled
41 If your operating system handles symlinks, built modules source code will be
42 available at the root of `gst-build/` for example GStreamer core will be in
43 `gstreamer/`. Otherwise they will be present in `subprojects/`. You can simply
44 hack in there and to rebuild you just need to rerun `ninja -C build/`.
46 ## Update git subprojects
48 We added a special `update` target to update subprojects (it uses `git pull
49 --rebase` meaning you should always make sure the branches you work on are
50 following the right upstream branch, you can set it with `git branch
51 --set-upstream-to origin/master` if you are working on `gst-build` master
54 Update all GStreamer modules and rebuild:
57 ninja -C build/ update
60 Update all GStreamer modules without rebuilding:
63 ninja -C build/ git-update
67 ## Add information about GStreamer development environment in your prompt line
71 We automatically handle `bash` and set `$PS1` accordingly
75 In your `.zshrc`, you should add something like:
78 export PROMPT="$GST_ENV-$PROMPT"
83 In your powerline theme configuration file (by default in
84 `{POWERLINE INSTALLATION DIR}/config_files/themes/shell/default.json`)
85 you should add a new environment segment as follow:
89 "function": "powerline.segments.common.env.environment",
90 "args": { "variable": "GST_ENV" },