2016-10-26 20:44:19 +00:00
# gst-build
2016-08-24 15:10:21 +00:00
2016-08-26 01:13:40 +00:00
GStreamer [meson ](http://mesonbuild.com/ ) based repositories aggregrator
2016-08-24 15:10:21 +00:00
2016-10-26 20:58:16 +00:00
You can build GStreamer and all its modules at once using
meson and its [subproject ](https://github.com/mesonbuild/meson/wiki/Subprojects ) feature.
2016-08-24 15:10:21 +00:00
2016-10-10 23:14:50 +00:00
## Getting started
2016-10-26 20:58:16 +00:00
### Install meson and ninja
2016-10-10 23:14:50 +00:00
2019-03-29 13:23:51 +00:00
Meson 0.48 or newer is required.
2016-10-26 20:58:16 +00:00
You should get meson through your package manager or using:
$ pip3 install --user meson
2019-03-29 13:23:51 +00:00
This will install meson into ~/.local/bin which may or may not be included
automatically in your PATH by default.
2018-10-28 16:05:23 +00:00
If you are building on Windows, do not use the Meson MSI installer since it is
experimental and will likely not work.
2019-03-29 13:23:51 +00:00
You can also run meson directly from a meson git checkout if you like.
2018-10-28 16:05:23 +00:00
You should get `ninja` using your package manager or download the [official
release](https://github.com/ninja-build/ninja/releases) and put it in your PATH.
2016-10-26 20:58:16 +00:00
### Build GStreamer and its modules
You can get all GStreamer built running:
2016-10-14 08:31:38 +00:00
2016-10-10 23:14:50 +00:00
```
2016-10-26 20:58:16 +00:00
mkdir build/ & & meson build & & ninja -C build/
2016-10-10 23:14:50 +00:00
```
2016-10-26 20:58:16 +00:00
NOTE: on fedora (and maybe other distributions) replace `ninja` with `ninja-build`
# Development environment
2016-08-24 15:10:21 +00:00
2016-11-07 21:17:39 +00:00
## Uninstalled environment
2016-10-26 20:58:16 +00:00
gst-build also contains a special `uninstalled` target that lets you enter an
2016-11-07 21:17:39 +00:00
uninstalled development environment where you will be able to work on GStreamer
easily. You can get into that environment running:
2016-08-24 15:10:21 +00:00
2016-10-26 20:58:16 +00:00
```
ninja -C build/ uninstalled
```
2016-08-24 15:10:21 +00:00
2016-11-07 21:17:39 +00:00
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/` .
2017-08-21 14:57:29 +00:00
NOTE: In the uninstalled environment, a fully usable prefix is also configured
in `gst-build/prefix` where you can install any extra dependency/project.
2016-11-07 21:17:39 +00:00
## 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
```
2016-11-02 18:40:54 +00:00
2017-03-07 23:31:26 +00:00
## Custom subprojects
We also added a meson option, 'custom_subprojects', that allows the user
to provide a comma-separated list of subprojects that should be built
alongside the default ones.
To use it:
```
cd subprojects
git clone my_subproject
cd ../build
rm -rf * & & meson .. -Dcustom_subprojects=my_subproject
ninja
```
2017-01-02 12:18:37 +00:00
## Run tests
You can easily run the test of all the components:
```
2018-02-05 15:44:40 +00:00
meson test -C build
2017-01-02 12:18:37 +00:00
```
2017-01-30 08:08:59 +00:00
To list all available tests:
```
2018-02-05 15:44:40 +00:00
meson test -C build --list
2017-01-30 08:08:59 +00:00
```
To run all the tests of a specific component:
```
2018-02-05 15:44:40 +00:00
meson test -C build --suite gst-plugins-base
2017-01-30 08:08:59 +00:00
```
2018-02-05 15:48:41 +00:00
Or to run a specific test file:
2017-01-02 12:18:37 +00:00
```
2018-02-05 15:46:00 +00:00
meson test -C build/ --suite gstreamer gst_gstbuffer
2017-01-02 12:18:37 +00:00
```
2016-11-02 18:40:54 +00:00
2018-02-05 15:48:41 +00:00
Run a specific test from a specific test file:
```
GST_CHECKS=test_subbuffer meson test -C build/ --suite gstreamer gst_gstbuffer
```
2018-02-22 12:14:26 +00:00
## Checkout another branch using worktrees
If you need to have several versions of GStreamer coexisting (eg. `master` and `1.14` ),
you can use the `checkout-branch-worktree` script provided by `gst-build` . It allows you
to create a new `gst-build` environment with new checkout of all the GStreamer modules as
[git worktrees ](https://git-scm.com/docs/git-worktree ).
For example to get a fresh checkout of `gst-1.14` from a `gst-build` in master already
built in a `build` directory you can simply run:
```
./checkout-branch-worktree ../gst-1.14 1.14 -C build/
```
2016-11-02 18:40:54 +00:00
## Add information about GStreamer development environment in your prompt line
### Bash prompt
2019-03-08 16:38:43 +00:00
We automatically handle `bash` and set `$PS1` accordingly.
If the automatic `$PS1` override is not desired (maybe you have a fancy custom prompt), set the `$GST_BUILD_DISABLE_PS1_OVERRIDE` environment variable to `TRUE` and use `$GST_ENV` when setting the custom prompt, for example with a snippet like the following:
```bash
...
if [[ -n "${GST_ENV-}" ]];
then
PS1+="[ ${GST_ENV} ]"
fi
...
```
2016-11-02 18:40:54 +00:00
### Zsh prompt
In your `.zshrc` , you should add something like:
```
export PROMPT="$GST_ENV-$PROMPT"
```
2017-12-01 14:16:34 +00:00
### Fish prompt
In your `~/.config/fish/functions/fish_prompt.fish` , you should add something like this at the end of the fish_prompt function body:
```
if set -q GST_ENV
echo -n -s (set_color -b blue white) "(" (basename "$GST_ENV") ")" (set_color normal) " "
end
```
2016-11-02 18:40:54 +00:00
### 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
},
```