Re: [fluid-dev] LADSPA refactor branch

[Ahmed Eraiba]

Hi Marcus,

I used exactly this guide to build release 1.1.8 using visual studio 2010:

https://github.com/FluidSynth/fluidsynth/wiki/BuildingWithCMake

It works fine for the latest release (but not for the previous one 1.1.7)

I'm using a c# 2010 wrapper for 1.1.6 and 1.1.8 worked perfectly when I build it. 

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.

To tell exactly the root cause, is behind my knowledge. Sorry for my limited programming skills.

Regards, Ahmed

On 12 Nov 2017 9:07 pm, Marcus Weseloh <address@hidden> wrote:

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 for Win64 and hear the effects. So it seems to work... can you give more details about the error you are encountering?

Also, the "void function returns a value" are due to a recent change in master which I've incorporated into the ladspa branch. There's a discussion in the relevant commit on GitHub:

https://github.com/FluidSynth/fluidsynth/commit/b1d0db7d5c9f4ff3bd5cb6163083fe66fdd42c0e#commitcomment-25565182

All the best,

    Marcus

2017-11-12 12:35 GMT+01:00 Ahmed Eraiba <address@hidden>:

Hi Marcus,

Thank you, just tried the last fix. It builds successfully (with the same warnings "void function returns a value"), but the fluid setting object faild to set string parameters, fluid_settings_setstr function throws exceptions.

Regards, Ahmed

On 12 Nov 2017 12:01 pm, Marcus Weseloh <address@hidden> wrote:

Hi again,

2017-11-12 2:05 GMT+01:00 Ahmed Eraiba <address@hidden>:

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 like a real problem. It should probably be _strnicmp for Windows, not _strincmp. I've pushed a fix to the ladspa branch.

Cheers,

    Marcus 

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