summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorCharlie Turner <mail@charles.plus>2020-01-06 13:22:54 +0000
committerCharlie Turner <mail@charles.plus>2020-01-06 21:06:42 +0000
commitc57dca5220a2f121331d46691aadb8e7f3168f75 (patch)
treea82b472ddf2b5cf4c59f0a08fd3b820497fd66fc /README.md
parent7aaa11aa772053eb82617eb92b5f4ff7424ec3d1 (diff)
downloadgstreamer-c57dca5220a2f121331d46691aadb8e7f3168f75.tar.gz
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.
Diffstat (limited to 'README.md')
-rw-r--r--README.md10
1 files changed, 10 insertions, 0 deletions
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: