[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fluid-dev] LADSPA refactor branch
From: |
Tom M. |
Subject: |
Re: [fluid-dev] LADSPA refactor branch |
Date: |
Sat, 11 Nov 2017 22:39:10 +0100 |
> But it seems like glib includes cross-platform dynamic library loading
> functions. So maybe I could switch to using those. (Tom... any objections to
> that?)
Not at all. That's exactly the reason we have glib for (...and the reason we'll
never get rid of it ;) )
You could think about wraping those calls in custom FLUID_DL* macros... but at
least I would not require you to do so. I consider it unlikely that some
windows user, who overrides fluid_sys.h and fluidsynth_priv.h, wants to compile
fluidsynth with ladspa support.
Tom
Am Samstag, 11. November 2017, 21:36:44 CET schrieb Marcus Weseloh:
> Hi Ahmed,
>
> great that you want to test it on Windows! But I'm not surprised that it
> doesn't work... the code uses dlopen from dlfcn.h and that isn't available
> for Windows (or so I've read... don't really have any experience with
> writing code for Windows).
>
> But it seems like glib includes cross-platform dynamic library loading
> functions. So maybe I could switch to using those. (Tom... any objections
> to that?)
>
> Cheers,
>
> Marcus
>
> 2017-11-11 21:20 GMT+01:00 Ahmed Eraiba <address@hidden>:
>
> > 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:
> > https://github.com/FluidSynth/fluidsynth/commit/
> > be2db6082d10c7aedc91a85b1ed0a0568554bab7
> >
> > 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
> >
> >
>
- [fluid-dev] LADSPA refactor branch, Marcus Weseloh, 2017/11/07
- Re: [fluid-dev] LADSPA refactor branch, Ahmed Eraiba, 2017/11/11
- Re: [fluid-dev] LADSPA refactor branch, Marcus Weseloh, 2017/11/11
- Re: [fluid-dev] LADSPA refactor branch,
Tom M. <=
- Re: [fluid-dev] LADSPA refactor branch, Marcus Weseloh, 2017/11/11
- Re: [fluid-dev] LADSPA refactor branch, Ahmed Eraiba, 2017/11/11
- Re: [fluid-dev] LADSPA refactor branch, Marcus Weseloh, 2017/11/12
- Re: [fluid-dev] LADSPA refactor branch, Marcus Weseloh, 2017/11/12
- Re: [fluid-dev] LADSPA refactor branch, Ahmed Eraiba, 2017/11/12
- Re: [fluid-dev] LADSPA refactor branch, Marcus Weseloh, 2017/11/12
Re: [fluid-dev] LADSPA refactor branch, Ceresa Jean-Jacques, 2017/11/12
Re: [fluid-dev] LADSPA refactor branch, Ahmed Eraiba, 2017/11/12