After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793166 - Please explain how to use the gst-build uninstalled environment
Please explain how to use the gst-build uninstalled environment
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-build
unspecified
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-02-04 14:49 UTC by nh2
Modified: 2018-11-03 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nh2 2018-02-04 14:49:35 UTC
I got very confused by https://github.com/GStreamer/gst-build/tree/c938c7591612b511cabfcf0b1788b10021186bf1#uninstalled-environment

Nothing in those docs indicated that I should call the script with the name of my shell as the first argument, e.g. `./gst-uninstalled.py bash` or `./gst-uninstalled.py zsh`, to get into the development environment.

Even though that program uses python's `argparse` CLI parser, it doesn't indicate in the help text, or in the linked README, that this should be done.

I only got the idea of how to use it by reading the code here: https://github.com/GStreamer/gst-build/blob/c938c7591612b511cabfcf0b1788b10021186bf1/gst-uninstalled.py#L230

Please add it to the docs and to the argparse `--help` output, thanks!
Comment 1 Tim-Philipp Müller 2018-02-08 11:54:18 UTC
Thanks for the bug report.

I don't think you're supposed to run the script yourself.

You're supposed to use 'ninja uninstalled' which will then run the script for you.

If this doesn't work for you for some reason, then perhaps the script needs fixing?

Could you provide more information on what didn't work if you follow the instructions in the README?
Comment 2 Nicolas Dufresne (ndufresne) 2018-02-23 02:54:25 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!
Comment 3 nh2 2018-02-23 17:17:37 UTC
I think conceptually the script works when run through ninja.

The reason I had to run it myself was to track down a bug with it (as part of https://github.com/centricular/gstwebrtc-demos/issues/2#issuecomment-362925247) where it would do O(n²) many appends and also make paths too long by adding them multiple times, so long that I couldn't start anything any more.

The reason I asked to improve the argparse parser to document exactly what the args to be passed are is that it would make that kind of investigation / bug-trackdown much easier to do.
Comment 4 GStreamer system administrator 2018-11-03 11:05:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-build/issues/7.