Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Ceresa Jean-Jacques
Hi, Ahmed and Marcus   Thanks to both for your informations, anyway there is something wrong. @ Marcus. 1)If Marcus said that only a ladspa.h is necessary to build FluidSynth that means that Marcus has written all the necessary LADSPA host code inside FluidSynth sources files. 1.1) The lads

Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Marcus Weseloh
Hi Ahmed, 2017-11-13 0:30 GMT+01:00 Ahmed Eraiba : > The last committs with LADSPA support builds successfully after the last > fix but the synth failed to initialise, as any call to function > fluid_settings_setstr > throws an exeption. > > Could you maybe try to build the latest master branch

Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Marcus Weseloh
Hi JJC, 2017-11-12 22:44 GMT+01:00 Ceresa Jean-Jacques < jean-jacques.cer...@orange.fr>: > A) I was wondering if a LADSPA library exists for Windows OS ?. > LADSPA is not really a library. It's a single header file: http://ladspa.org/ladspa_sdk/ladspa.h.txt. So all you have to do to enable LADSPA

Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Ceresa Jean-Jacques
Hello,   A) I was wondering if a LADSPA library exists for Windows OS ?. I guess and assume that in the intend of building (FluidSynth + LADSPA) on Windows we may use the usual walking steps ? 1) Install this unknow LADSPA library for Windows somewhere to get it visible by Cmake. 2) Run Cmak

Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Marcus Weseloh
Hi Ahmed, I just installed Visual Studio 2017 on my Windows 10 machine, downloaded the latest glib, glib-dev, pkg-config, proxy-libintl and gettext, copied the ladspa.h file into the VS include dir and ran cmake. Then I built the project and ran fluidsynth. I could load a LADSPA plugin compiled f

Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Marcus Weseloh
Hi again, 2017-11-12 2:05 GMT+01:00 Ahmed Eraiba : > >> I pulled the last commit and recreated a new make but build failed, >> giving this error: >> >> fluid_ladspa.obj : error LNK2019: unresolved external symbol __strincmp >> referenced in function _get_effect_port_idx >> > Actually, this looks l

Re: [fluid-dev] LADSPA refactor branch

2017-11-12 Thread Marcus Weseloh
Hi Ahmed, 2017-11-12 2:05 GMT+01:00 Ahmed Eraiba : > I pulled the last commit and recreated a new make but build failed, giving > this error: > > fluid_ladspa.obj : error LNK2019: unresolved external symbol __strincmp > referenced in function _get_effect_port_idx > > Also so many "void function r