[Top][All Lists]

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

Re: [fluid-dev] FluidSynth 2.0 beta talk

From: Marcus Weseloh
Subject: Re: [fluid-dev] FluidSynth 2.0 beta talk
Date: Thu, 31 May 2018 09:35:50 +0200

Hi Andreas,

With FluidSynth 2.0 the API has changed in a few places. fluid_preset is now an opaque type that should only be used as a pointer and accessed via accessor functions.

I had a quick try to fix the relevant code in fluidsynth-dssi (in fsd_get_soundfont), but noticed that we have not exposed the fluid_preset_get_* accessor functions. 
I've created an issue on GitHub about his: https://github.com/FluidSynth/fluidsynth/issues/391



2018-05-31 1:15 GMT+02:00 Andreas Müller <address@hidden>:

To give the new release a test I started a build (Openembedded). I am
coming from fluidsynth 1.1.11 and all build and worked fine so far.

I see build errors on:

* fluidsynth-dssi 1.0.0 from my git repo: compile
* csound from git: compile
* qsynth 0.5.1: compile error
* ardour5 5.12 (that compiled and installed fine - packaga qa failed - ignore)
* carla/carla from git/bit outdated: compile
* calf-studio-gear 0.90.0 compile

Looking into the first (fluidsynth-dssi) I see:

| ../../git/src/fluidsynth-dssi.c:173:20: error: storage size of
'preset' isn't known
      fluid_preset_t preset;
|                     ^~~~~~
| ../../git/src/fluidsynth-dssi.c:212:16: error: dereferencing pointer
to incomplete type 'fluid_sfont_t {aka struct _fluid_sfont_t}'
|     fluid_sfont->iteration_start(fluid_sfont);
|                ^~

The only kind of 'definition' I find for fluid_preset_t is in

typedef struct _fluid_sfont_t fluid_sfont_t;                    /**<
SoundFont */

That is not much and grepping for _fluid_sfont_t gives only this
occurance so I would agree with the compiler. What goes wrong - or
what configuration option am I missing for fluidsynth?

Fluidsyth was configured with
-Denable-floats=ON -DLIB_SUFFIX=  -Denable-jack-support=ON
-Denable-portaudio=ON -Denable-pulseaudio=ON

Help appreciated :)


fluid-dev mailing list

reply via email to

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