On Friday 15 April 2011, Sven Meier wrote:
> > The coreaudio driver .. Now it is based on AUHAL.
>
> So CoreServices are required? I wonder how you were able to build
> fluidsynth without the include.
Probably because I run a Mac OSX version different than yours. Mine is Leopard
(10.5), and yo
Hi Pedro,
> new build option "enable-framework", true by default in Mac OSX.
sorry, I missed your announcement. Disabling this option worked as
advertised, now I have my libfluidsynth.dylib ;).
> The coreaudio driver .. Now it is based on AUHAL.
So CoreServices are required? I wonder how you
On Thursday 14 April 2011, Sven Meier wrote:
> Hi all,
>
> I've just built fluidsynth on OS X but it seems I've forgotten some details
> on how it worked the last time ;).
>
> I had to add an include to fluid_coreaudio.c or the build would have
> complained about an undeclared 'ComponentDescrip
On Apr 14, 2011, at 4:25 PM, Sven Meier wrote:
BTW why is it that the resulting shared library is named
"Fluidsynth"? Wouldn't libfluidsynth.dylib be more appropriate?
Sven
Many thanks for your testing earlier.
If you build with the enable-framework option you will build an OS X
framewor
Hi all,
I've just built fluidsynth on OS X but it seems I've forgotten some details on
how it worked the last time ;).
I had to add an include to fluid_coreaudio.c or the build would have complained
about an undeclared 'ComponentDescription’:
#include
Any idea what might have required
