Compiling into a statically-linked DLL #1001
Replies: 2 comments 2 replies
-
What exactly makes this a burden? You just have multiple DLLs and ship them in the same directory. That's it, isn't it? If there's a bug in fluidsynth, you replace the fluidsynth.dll. If there's a bug in libsndfile, you replace libsndfile.dll, etc... IMO, the real burden is getting such a customized build working (and maintainable!) which you're asking for. Esp. because glib cannot be statically compiled on Windows, IIRC. |
Beta Was this translation helpful? Give feedback.
-
This is a good idea and I have implemented just now: |
Beta Was this translation helpful? Give feedback.
-
Some projects, like 86Box/86Box (which I help maintain) and coelckers/gzdoom, ship their Windows builds with an ancient version of FluidSynth compiled into a single statically-linked DLL, to avoid the burden of shipping separate DLLs for each of FluidSynth's dependencies (libgcc, glib and so on). That DLL was built many years ago by an unknown person out of an unknown FluidSynth 1.x codebase through unknown means. Therefore, it would be interesting to have an officially-supported way to compile a modern version of FluidSynth into a single DLL, or a single dynamic library on other platforms (though Windows is my main concern). I have attempted to produce a single DLL myself, either through modifying the CMake definitions or running the static library through
dllwrap
, but I haven't had any luck.Beta Was this translation helpful? Give feedback.
All reactions