[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] making a standalone fluidsynth plugin on Mac

From: Antoine Schmitt
Subject: Re: [fluid-dev] making a standalone fluidsynth plugin on Mac
Date: Wed, 28 Mar 2012 14:55:45 +0200

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.

Now, Windows... Any advice to save me some sweat ?


Le 28 mars 12 à 05:05, R.L. Horn a écrit :

On Wed, 28 Mar 2012, Antoine Schmitt wrote:

Or is glib installed on all linux machines by default,

Pretty much.

As far as libffi is concerned, you could try an older version of glib (earlier than April, 2011, or thereabouts) that doesn't have that dependency. FWIW, you're not alone in your frustration...a lot of us ophidiophobes were royally POd about that.

The mandatory gettext dependency is also just plain obnoxious if you don't require NLS. Unfortunately, short of providing a dummy libintl, I'm not sure what can be done about it. The good news is that, if you only want English, you can safely throw away the locale files.

Just for kicks, I built a static version of glib-2.16.5 (the newest "old" version I had at hand) and was able to build a functional fluidsynth with no special dependencies (well, except for gettext and iconv, which are built into glibc).

It can be done. Fairly easily. Under linux. Which may or may not be of any relevance whatsoever.

The threads error is a real mystery. What do you get when you run "otool -L" on fluidsynth versus your app?

fluid-dev mailing list

++ as :: Antoine Schmitt

reply via email to

[Prev in Thread] Current Thread [Next in Thread]