fluid-dev
[Top][All Lists]
Advanced

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

Re: [fluid-dev] LADSPA refactor branch


From: Ceresa Jean-Jacques
Subject: Re: [fluid-dev] LADSPA refactor branch
Date: Sun, 12 Nov 2017 22:44:50 +0100 (CET)

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 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" <address@hidden>
> A : "FluidSynth mailing list" <address@hidden>
> 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 <address@hidden> 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:

>
It that understandable and explains it in enough detail?

>
Cheers,

>
   Marcus

>



_______________________________________________
fluid-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fluid-dev


reply via email to

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