Re: [fluid-dev] About Supporting 2GiB+ Soundfonts on Windows

2020-03-16 Thread Reinhold Hoffmann
We (still) use Visual Studio 2010 and use __int3264 which redirects to __int64 for 64 bit. === code snipset from BaseTsd.h which is part of VS2010 === // // The INT_PTR is guaranteed to be the same si

Re: [fluid-dev] About Supporting 2GiB+ Soundfonts on Windows

2020-03-16 Thread Dan Eble
On Mar 16, 2020, at 09:57, Tom M. via fluid-dev wrote: > The current workaround is to build fluidsynth with CygWin, which has "long" > set to 64bit. > > Any ideas how to solve this? Opinions on C99? If you decided to require C99, I would think you would want to use int64_t and its relatives fo

[fluid-dev] About Supporting 2GiB+ Soundfonts on Windows

2020-03-16 Thread Tom M. via fluid-dev
We have a bug report on GitHub [1]: A user reports that loading Soundfonts >2GiB fails on Win10 64bit. There are two factors making up the root cause: 1. The ANSI C file API, namely ftell() and fseek(), use "long" as data type for specifying offsets in the file. 2. Even on 64bit Windows, "long"