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 ladspa.h seems only necessary for the LADSPA host code to reference the external plugins (usualy in shared library .so on Linux .dll on Windows) to be loaded 1.2) Consequently there is no need of a LADSPA library (regardless this library would be static (i.e xxx.lib) or dynamic (.i.e xxx.dll). 1.3) That means that the unknow library installed by Ahmed is unuseful. @ Ahmed 1.4) Please what it the name file of the LADSPA library you have installed. ladspa.h is not a library. @ Ahmed >I'm using a c# 2010 wrapper for 1.1.6 and 1.1.8 worked perfectly when I build >it. Even this question is not related to your recent LADSPA buiding issue, why did you use a c# wrapper ? Again thanks for your informations. Regards > Message du 13/11/17 01:08 > De : "Ahmed Eraiba" > A : "FluidSynth mailing list" , "Ceresa Jean-Jacques" > Copie à : > Objet : Re: [fluid-dev] LADSPA refactor branch > > Hi jjc, > Here are what I already did up to now willing to try LADSPA for windows: > A) Yes there is a LADSPA lib for Windows > 1) I installed LADSPA lib, but ladspa.h must be in include folder. So I did. The cmake should output ladspa.h - found > 2) the last committs has both win and ladspa checked by default. > C) Build was successful for me with both visual studio and minGW. But it doesn't work for me. > I'm stuck at this step so far... > Regards, Ahmed > > > On 12 Nov 2017 11:44 pm, Ceresa Jean-Jacques wrote: > Hi > > 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 Cmake and choose the 2 options: > - Windows > - LADSPA > 3) Than build FluidSynth ( using MSVS for example if MSVS was choosed during > Cmake). > > B)Or perhaps, the necessary source LADSPA library is already in FluidSynth > sources ready to be compiled if the LADSPA option is set during Cmake ?. > > C) Assuming the build for Windows compile with success: > - c1) At execution time, how externals plugings (for windows) could be found > and loaded compared to the usual way on Linux ?. > - c2) Does new LADSPA plugings for Windows could be build the usual way on > Linux (even this question is a bit out the scope) ? > > Thanks a lot for any possible clarifications on theses questions ?. > Regards. > > Message du 11/11/17 21:21 > > De : "Ahmed Eraiba" > > A : "FluidSynth mailing list" > > Copie à : > > Objet : Re: [fluid-dev] LADSPA refactor branch > > > > Hi All, > > I would like to try this for windows. I usually configure and generate by cmake for visual studio 2010. The original 1.1.8 can be successfuly built, but not for this one with LADSPA support. > > It gives a "cannot open include file dlfcn.h" error, but this file also depends on fearures.h and then "bits/dlfcn.h" (is it a different version of dlfcn.h?) But as I don't know much about LADSPA or its dependencies, could anybody help me on how to start making a successful try for windows? Thanks a lot! > > Regards, Ahmed > > > > On 11 Nov 2017 6:54 pm, Marcus Weseloh wrote: > Hi again, > > I've added some more documentation that hopefully explains the effect signal paths in FluidSynth and how to replace the internal effects with LADSPA plugins: https://github.com/FluidSynth/fluidsynth/commit/be2db6082d10c7aedc91a85b1ed0a0568554bab7 > > > > It that understandable and explains it in enough detail? > > Cheers, > > Marcus > > > > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev > > >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
