Well, actually, this plugin already exists :
http://www.schmittmachine.com/fluidXtra.html
But it was based on fuidsynth1.0.7
I wanted to port it to 1.1.5 in order to benefit from new features
like sound output selection, and also bug fixes.
I thought that it would be a breeze, but it appeared t
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 inte
Just to be clear for future developers in the same situation (building
a standalone executable on MacOSX dependent on fluidsynth), the
solution for me was to copy all the fluidsynth dependencies
(recursively) into the executable package and use install_name_tool to
have the executable point
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
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
Indeed, and the pitfall in which I am now was clearly mentionned
already then... ;(
Ok, so my only solution is to build a static glib on Mac and on Windows.
Pray for me
Le 28 mars 12 à 01:20, Ebrahim Mayat a écrit :
On Mar 27, 2012, at 6:47 PM, Antoine Schmitt wrote:
Thanks Ebrahim.
T
On Mar 27, 2012, at 6:47 PM, Antoine Schmitt wrote:
Thanks Ebrahim.
This is incredibly complex !
I cannot believe that I am the only one having this problem. How do
you people deploy fluidsynth-based executables on machines that do
not have glib installed ? Or is glib installed on all linux
Thanks Ebrahim.
This is incredibly complex !
I cannot believe that I am the only one having this problem. How do
you people deploy fluidsynth-based executables on machines that do not
have glib installed ? Or is glib installed on all linux machines by
default, and this is a Mac and Windows-o
On Mar 25, 2012, at 5:48 PM, Antoine Schmitt wrote:
Hi list,
coming back on this. I stippped down my dependencies, and now my
Xtra only depends on glib and gthread.
But now I am stuck again, trying to not depend on these shlibs.
- I used Sven install_name_tool idea, which seems to work and l
Hi list,
coming back on this. I stippped down my dependencies, and now my Xtra
only depends on glib and gthread.
But now I am stuck again, trying to not depend on these shlibs.
- I used Sven install_name_tool idea, which seems to work and load the
locally copied shlibs, but then it crashes my
On Saturday 10 March 2012, Antoine Schmitt wrote:
Hi list,
I'm currently porting my fluidsynth Xtra (name for Adobe Director
plugin, i.e. a shared library that is dynamically loaded into the
final executable) to fluidsynth 1.1.5. Previously, it was on 1.0.7.
(visible on www.schmittmachine.com/flu
Hi,
for jOrgan I use homebrew to build Fluidsynth on OS X:
http://sourceforge.net/apps/trac/fluidsynth/wiki/BuildingWithCMake#BuildingonOSX
I then use install_name_tool to tweak the loader_path of all
dependencies. This allows me to bundle all required libraries into my
application.
H
On Sunday 11 March 2012, R.L. Horn wrote:
> ./configure --without-readline
> ./configure --disable-dbus-support
> ./configure --disable-libsndfile-support
The auto-tools build system for FluidSynth is deprecated. The cmake build
system has equivalent options:
cmake -Denable-readline=off -Denabl
On Saturday 10 March 2012, Antoine Schmitt wrote:
> Hi list,
> I'm currently porting my fluidsynth Xtra (name for Adobe Director
> plugin, i.e. a shared library that is dynamically loaded into the
> final executable) to fluidsynth 1.1.5. Previously, it was on 1.0.7.
> (visible on www.schmittm
On Sat, 10 Mar 2012, Antoine Schmitt wrote:
My problem is that I end up with an Xtra (DLL) that depends on many fink
shared libraries, which are not available on the end-user system,
/usr/local/lib/libgthread-2.0.0.dylib
/usr/local/lib/libglib-2.0.0.dylib
GNU GLib: http:/
Hi list,
I'm currently porting my fluidsynth Xtra (name for Adobe Director
plugin, i.e. a shared library that is dynamically loaded into the
final executable) to fluidsynth 1.1.5. Previously, it was on 1.0.7.
(visible on www.schmittmachine.com/fluidXtra.html).
The big change is in the buil
16 matches
Mail list logo