Hi,

Thanks for the pointers. I wasn't using Cmake, so I will try again using
it. The older instructions didn't mention it, so I will try again.

Another related question: should I leave the visual studio folder where it
is or do I need to move it? The instructions seemed to imply that I had to
move it. Maybe that was a mistake that I made.

On Tue, Sep 26, 2017 at 9:36 AM, Ceresa Jean-Jacques <
jean-jacques.cer...@orange.fr> wrote:

> Hi, Hugo and Tom
>
>
>
> Just for information.
>
> I have followed the instructions (long time ago) on the Wiki page to
> configure with Cmake to build FluidSynth v 1.1.3 with Visual Studio (vs
> 6.0).
>
>
>
> 1)The normal difficulty encountered was (as far i remember) , the
> dependencies packages referenced by Cmake (glib (mandatory), and others
> components options chosen by the developper in the Cmake GUI).
>
> We need to run Cmake several times as it help to identify the necessary
> packages. Once theses package are installed, Cmake find Vs 6.0 and Vs 10
> (but i have choosen Vs6.0 ).
>
> The log of Cmake was  success (Generating done). Cmake have generated the
> project files for Vs6.0.
>
>
>
> 2)The following steps are the building process using Visual Studio.
>
> Notes: Here are the 3 errors and temporary fix encountered at build time:
>
>
>
>
>
> 2.1) In fluid_phase.h (since or before v 1.0.9)
> type typedef unsigned long long fluid_phase_t; is not  accepted.
>
> fix: I have replaced this type by ULONGLONG.
> (In macros,  unsigned long long  has been replaced par fluid_phase_t).
>
>
>
> 2.2)In fluid_winmidi.c: type  DWORD_PTR has not be found
>
> fix: I think there is a missing .h somewhere. I have temporary replaced
> DWORD_PTR  by DWORD (waiting for the best fix).
>
>
> 2.3)In fluid_sys.c:
> function fluid_server_socket_run(). unresolved.
> fix: The function calling inet_ntop() has been replaced by those of v
> 1.1.3 (waiting for a best fix).
>
>
>
> 3)As usual, at execution time we need to set the Path variable to point on
> the directory dlls ( glib dlls, others dlls ).
>
>
>
> I have followed theses steps for FluidSynth since v1.0.9 (without Cmake),
> v1.1.3 until v 1.1.6 (with Cmake) and the difficulties was of
>
> the same order (not fully painless but not too complicated).
>
>
>
> As Tom say, Cmake log and Vs log  will be helpful to adapt the wiki page
> if necessary.
>
>
>
> Cheers.
>
>
>
> jjc
>
>
>
> > Message du 26/09/17 08:52
> > De : "Tom M." <tom.m...@googlemail.com>
> > A : "FluidSynth mailing list" <fluid-dev@nongnu.org>
> > Copie à :
> > Objet : Re: [fluid-dev] What is the recommended way to build in windows
> right now?
>
> >
> >
> It should work with Visual Studio, though the instructions on the wiki
> page are surely old and might need an update. I cant really help with
> Visual Studio. I know it's usually a pain to get it work. However the wiki
> should be editable by any registered github user, so anyone is free to
> update it or simply clone the wiki locally, edit the markdown and email me
> any suggestions.
> >
> >
> Hugo: You could however tell us which version of fluidsynth you were using
> and whether you were using cmake or autotools. And providing a full build
> log might also help.
> >
> >
> Tom
> >
> >
>
> >
> 2017-09-26 3:44 GMT+02:00 Hugo Estrada <hugoe...@gmail.com>:
> >
>>
>> Hi,
>>
>> >
>> I followed the visual studio instructions found in the github wiki to
>> build fluidsynth. I kept solving one problem after another until I I
>> couldn't seem to move forward. This makes me feel that those instructions
>> may be old, and that the Visual Studio solution and build is not supported
>> anymore.
>> >
>>
>> >
>> I see instructions with cmake, and instructions with mingw and msys . I
>> cannot use cygwin, it doesn't work well on my machine.  So what would be
>> the recommended way to build in windows now?
>>
>> >
>> Thanks in advance,
>>
>> >
>> Hugo
>>
>> > _______________________________________________
>> > 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
>
>
> _______________________________________________
> 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

Reply via email to