|
From: | Antoine Schmitt |
Subject: | Re: [fluid-dev] making a standalone fluidsynth plugin on Windows |
Date: | Mon, 2 Apr 2012 22:52:31 +0200 |
Hi list !ok, I changed the subject of the message, because I am not having the same problem on Windows... I installed glib, gthread, intl, etc.. and I now have a running plugin on Windows. But again, it depends on the glib and gthread DLLs, so it cannot run on a deployment system without installing glib+gthread on this system, which is not possible for an end-user. I need a standalone plugin again.
I tried to explicitely link my plugin against the .lib versions of glib/gthread, but in the end Depends.exe tells me that it still depends on the DLLs.
The DLLs are in /freesw/bin : libglib-2.0-0.dll etc.. And the libs are in /freesw/lib : glib-2.0.lib etc..Do we also have a magical solution like on Mac (install_name_tool) ? Or some other solution ?
Thank you very much
On Mar 28, 2012, at 8:55 AM, Antoine Schmitt wrote:Ok !Cross-reading your answer, adn Ebrahim's, I figured that I needed to include all the closure of the dependencies along with my delivery : glib and gthread, but also iconv and intl, and use install_name_tool to modify all mutual interdependencies between the executable and all the libs, and between the libs themselves too.And it works ! Thank you very much.
++ as :: Antoine Schmitt
[Prev in Thread] | Current Thread | [Next in Thread] |