#7694 closed feature request (wontfix)
Check the version of fluidsynth in configure script
Reported by: | SF/mac_es | Owned by: | Kirben |
---|---|---|---|
Priority: | normal | Component: | Port: Win32 |
Version: | Keywords: | ||
Cc: | Game: |
Description
I opened a bug because compiling whith fluidsynth in cygwin environment and linking dsound library was hanging scummvm.
I was told that it was for compiling whith fluidsynth 1.0.8 in static way. Also, I was informed that cygwin's support was dropped.
The problem is that I was unable to compile fluidsynth so I was using the precompiled win32 built of 1.0.0 (newers were complaining about missing defines). Now I was able to compile 1.0.8 and everything is working now fine. So, I guess that the version should be checked.
The version is defined in fluidsynth/version.h whith a line #define FLUIDSYNTH_VERSION "1.0.8"
BTW, how the hell have you manage to compile the library as a static library? I have compiled but if I disable shared or link it statically it complains about missing implementations of functions...
Also, I'm migrating to MSYS/mingw environment. But msys is having troubles whith heap in Windows and ususally hangs everywhere. I have tried rebasing the dll, updating it... any ideas?
Thanks
Ticket imported from: #2727895. Ticket imported from: feature-requests/510.
Attachments (1)
Change History (4)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Owner: | set to |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
comment:3 by , 6 years ago
Component: | → Port: Win32 |
---|
We don't know exactly how that particular precompiled fluidsnyth 1.0.0 library was even built. It could have been built with Microsoft VC++ (requiring -mms-bitfields), or be a conflict been different DirectSound libraries been linked in, but they are just guesses.
I really don't see any reason to look further into this issue, considering you can only confirm it occurs in a precompiled binary, and that fluidsynth 1.0.0 is ancient now.
Use the attached patch, if you want to compile a static build of fluidsynth. Unfortunately the build system of fluidsynth 1.0.8 always assumes a dynamic build under Windows, so I simply hacked around it.
No ideas on your heap issues under msys, I can only suggest asking on their mailing list.