From c57dca5220a2f121331d46691aadb8e7f3168f75 Mon Sep 17 00:00:00 2001
From: Charlie Turner <mail@charles.plus>
Date: Mon, 6 Jan 2020 13:22:54 +0000
Subject: dev environment: allow printing only env without starting a shell

allow for workflows that don't want the gst scripts to start shells,
this can be awkward for higher-level scripts setting up shells
themselves.

this is especially useful in combination with eval, and mimics the sort
of thing you can do with ssh-agent -s.
---
 README.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

(limited to 'README.md')

diff --git a/README.md b/README.md
index ff16c00dde..c5b7c8591d 100644
--- a/README.md
+++ b/README.md
@@ -314,6 +314,16 @@ You can get into the development environment the usual way:
 ninja -C $BUILDDIR/ devenv
 ```
 
+Alternatively, if you'd rather not start a shell in your workflow, you
+can mutate the current environment into a suitable state like so:
+
+```
+gst-env.py --only-environment
+```
+
+This will print output suitable for an sh-compatible `eval` function,
+just like `ssh-agent -s`.
+
 After setting up [binfmt] to use wine for windows binaries,
 you can run GStreamer tools under wine by running:
 
-- 
cgit v1.2.1