#299 closed task (wontfix)
try newer gstreamer win32 builds
Reported by: | Antoine Martin | Owned by: | aradtechkk |
---|---|---|---|
Priority: | critical | Milestone: | 0.9 |
Component: | platforms | Version: | |
Keywords: | win32 | Cc: |
Description
In order to solve #297 reliably and to get opus support (#246), we probably need a better/newer build of gstreamer, it doesn't hurt to try.
The ossbuild downloads are stuck in March 2011 and it seems like the project is completely dead.
Maybe these 0.10 builds are more up to date? (latest from March 2012 - slightly better)
Alternatively, we could try porting it to gstreamer 1.0, but I think this is going to be a lot of work: we cannot use gtk2 as the new gstreamer/pygst bindings use gobject introspection.
Change History (2)
comment:1 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 Changed 17 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/299
Note: See
TracTickets for help on using
tickets.
OK, I want to make a release sooner rather than later so I've tried it myself and this looks like a no-go.
Here's how:
C:\gstreamer-0.10-win32
. Warning: DO NOT ever useC:\gstreamer
which is a "magic" path hardcoded somewhere in the win32 builds of gstreamer...win32/MAKE-INSTALLER.BAT
to match the new location:(the directory structure must be preserved to minimize the changes to the BAT file)
bin
to the xpra installation directory, and all the DLLs fromlib/gstreamer-0.10
togstreamer-0.10
in xpra's installation directoryUnfortunately the resulting .exe just hangs silently (looks like a DLL-hell issue), so we probably need to build the python bindings from source, against the headers from this latest build.. And that is totally non-trivial since you need a lot of headers to build (python headers, gtk headers, etc .. as well as the gstreamer headers, ideally all via pkgconfig). If possible, a cross build from Linux may well be an easier option.
The only real way forward is to sort out the win32 build completely... by not using the horror that is MS Windows as a build environment, see #300