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 762309 - soundtouch: Only static library available on Windows
soundtouch: Only static library available on Windows
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: cerbero
git master
Other Linux
: Normal normal
: 1.7.90
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-19 08:50 UTC by George Yunaev
Modified: 2016-02-20 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fixed static linking for wildmidi on win32 (458 bytes, patch)
2016-02-19 08:50 UTC, George Yunaev
rejected Details | Review

Description George Yunaev 2016-02-19 08:50:18 UTC
Created attachment 321638 [details] [review]
fixed static linking for wildmidi on win32

Currently gst wildmidi plugin can only link with a dynamic library. However I see most plugins link statically with their libraries. If this is desired for wildmidi, please apply this patch too.

This only affects Win32 platform.
Comment 1 Sebastian Dröge (slomo) 2016-02-19 15:35:39 UTC
All plugins should link dynamically with their libraries. Which don't and how do you check that?
Comment 2 George Yunaev 2016-02-19 20:14:48 UTC
soundtouch plugin doesn't, since its dynamic library is not even built :)
Comment 3 Sebastian Dröge (slomo) 2016-02-20 08:47:00 UTC
This should be fixed now. Are there any others where the shared library is missing?

commit a12b733d4f045a93df459282ea36faa4fc94f5ae
Author: Sebastian Dröge <sebastian@centricular.com>
Date:   Sat Feb 20 10:44:24 2016 +0200

    soundtouch: Try harder to build Win32 DLLs instead of just static libraries
    
    https://bugzilla.gnome.org/show_bug.cgi?id=762309
Comment 4 George Yunaev 2016-02-20 09:45:38 UTC
Dunno. I actually prefer shared libs, easier to figure out what to package. Overall GStreamer packaging and size is a major issue, and is the only significant disadvantage I've found so far with GStreamer against QMediaPlayer and FFMpeg (and I've used all three quite extensively).
Comment 5 Sebastian Dröge (slomo) 2016-02-20 10:12:41 UTC
You can get the size down dramatically if you remove all the files that you don't need. By default the binaries come with everything you might possibly want to use, which is much more than what the other two provide (and e.g. we include all of ffmpeg) :)