Environment variables suggestion
All-In-One PyGI/PyGObject for Windows Installer
Status: Abandoned
Brought to you by:
tumagonx
Menu
▾
▴
#36 Environment variables suggestion
Hello
I just installed pygi-aio-3.18.2_rev3 and noticed a lots of gst-launch windows (probably some checking).
However, all these fail on my system, since I also have Gstreamer0.1 installed, with the environment variables GST_PLUGIN_PATH and GST_PLUGIN_SYSTEM_PATH, which causes all these gst-launch to fail.
The workaround for this is to remove these variables from the environment, run the setup and put them back after and adding GST_PLUGIN_PATH_1_0 and GST_PLUGIN_SYSTEM_PATH_1_0.
Perhaps you could add GST_PLUGIN_PATH_1_0 and GST_PLUGIN_SYSTEM_PATH_1_0 to the environment before running gst-launch, maybe as an optional step.
Cheers, Tom
Thanks for the report.
It supposedly only one gst-inspect window for caching plugins (the registry.[arch].bin file).
That's quite unfortunate situation, I think gstreamer 0.10 could works without those envvars set (it will still scan its relative lib\gstreamer-0.10 i think). Afterall isn't you will still have trouble if you run pygi-based gstreamer app if GST_PLUGIN_PATH_1_0 or GST_PLUGIN_SYSTEM_PATH_1_0 not set?
Personally I'm against setting any system-wide envvars (just to be able to run a software), IMHO the idea of one centralized library under Windows is practically not possible as there is always reason an app would bundle their own runtime. Even Java know this well and wont set JAVA_HOME,
But it's not a really problem for PyGI, I still could use site-packages\rpath.pth to inject per-session envvars and override any other conflicting system-wide envvars.
Thanks again for the hints.
You just gave me an idea to set environment variables in .pth file for my Gstreamer 0.10 virtual environment and it looks OK, so there's no need to change anything in pygi-aio installation.
Thanks, Tom
I see, I thought that those envvars was set by GStreamer 0.10 SDK installer. So it wasn't.
Do I still need to take precaution?
Sorry for a late reply, I didn't see these comments earlier...
No, there's no need for a precaution, everything works fine without any modification in the setup procedure. I can just set these variables using .pth files in the appropriate virtual environment.
Thanks, Tom
I think I will apply it to rpath,pth, just in case.
closing.