Hello Tom, Thought I'd chime in, since I was the one who pushed using glib to begin with. I got tired of all the architecture specific code which seemed to have issues in certain situations and saw glib as being a good option. It does complicate building on those platforms though and in embedded systems use cases especially. I know FluidSynth used to have a wrapper interface which provided a lot of this architecture specific code and I suspect a good portion of this is still in place. Such a wrapper could be used to implement architecture specific ports which would not require glib. I'm fairly knowledgeable with glib's features and API, having used it for a long time in many applications, but I'm not too interested personally in creating arch specific FluidSynth ports, except perhaps the embedded systems case. I could probably answer questions as to the glib API which FluidSynth is using though.
I don't know much about C11 myself, so can't comment on that. Cheers! Element Green On Mon, Sep 18, 2017 at 11:41 AM, Tom M. <tom.m...@googlemail.com> wrote: > I would like to bring this up again. I can absolutely comprehend the > arguing of windows or mac users to get rid of glib. I would accept a patch > that makes fluidsynth get rid of glib and support Posix OSs and Windows. > However my personal preferred solution would be to go with C11. Stroustrup > has fortunately given us such a modern tool and the only reason not to use > it is because stupid VisualStudio doesnt support it. However VS supports > LLVM, so it should still be possible to build C11 programs via clang, not > sure how expensive it is to get that working though. > > Any thoughts on C11? > > Tom > > > 2016-06-30 22:02 GMT+02:00 Ryan Gonzalez <rym...@gmail.com>: > >> Great news! I finally got VirtualBox and Windows working again! >> Hopefully, I'll get the Windows side of things working tomorrow, but the >> WORST-CASE scenario would be early next week. >> >> On Mon, Jun 6, 2016 at 6:11 PM, Ryan Gonzalez <rym...@gmail.com> wrote: >> >>> No. Couldn't get the damn thing to install in a VM. >:( >>> >>> Anyone here interesting in helping on the Windows front? Please? At all? >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something’s wrong. >>> http://kirbyfan64.github.io/ >>> On Jun 6, 2016 5:58 PM, "Antoine Schmitt" <a...@gratin.org> wrote: >>> >>>> Any news on the windows/glib front ? >>>> >>>> >>>> Le 25 mai 2016 à 16:41, Ryan Gonzalez <rym...@gmail.com> a écrit : >>>> >>>> Unfortunately, I can't do anything on Windows now...because it won't >>>> boot. Hangs forever on the stupid wheel of death. Curse you, Microsoft... >>>> >>>> In a few days (hopefully over the long weekend!), I'll probably install >>>> the Windows 10 trial into a VM and see if I can work from there. >>>> >>>> On Linux, though, it should be glib-free. IIRC OSX should also work, >>>> provided you have a recent version of GCC. Windows is really the primary >>>> pain ATM. >>>> >>>> Link: https://github.com/kirbyfan64/fluidsynth >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something’s wrong. >>>> http://kirbyfan64.github.io/ >>>> On May 25, 2016 6:59 AM, "Antoine Schmitt" <a...@gratin.org> wrote: >>>> >>>>> Hi, >>>>> just wanted to know the status of the glib dependency removal process ? >>>>> >>>>> glib has been a high pain for me when porting to Windows and Mac. I'd >>>>> be happy to see it removed from fluidsynth and port my fluidXtra to a >>>>> glib-free fluid. >>>>> >>>>> Thanks >>>>> Antoine >>>>> >>>>> >>>>> Le 22 janv. 2016 à 00:13, Ryan Gonzalez <rym...@gmail.com> a écrit : >>>>> >>>>> Well, I've already ported over most glib utilities, atomics, and >>>>> mutexes (normal and recursive). I just ended up busy with several other >>>>> things until this weekend. >>>>> >>>>> On January 21, 2016 4:06:41 PM CST, Johannes Schickel < >>>>> lordh...@gmail.com> wrote: >>>>>> >>>>>> On 01/14/2016 12:29 AM, Ryan Gonzalez wrote: >>>>>> >>>>>>> May I try? :D >>>>>>> >>>>>>> Pretty much everything outside of threading is really trivial. The >>>>>>> wiki says the supported platforms are Windows, OSX, and Linux, and >>>>>>> that it runs under Solaris and OS/2 but they aren't officially >>>>>>> supported. >>>>>>> >>>>>>> For atomics, glib seems to use GCC's C++11-style atomics. when it can, >>>>>>> then it falls back to either GCC/Clang's built-in __sync atomic >>>>>>> operations or Windows's atomic API. >>>>>>> >>>>>>> For normal threads, glib uses pthreads on Posix and Windows threads >>>>>>> on...Windows. >>>>>>> >>>>>>> Maybe I'm just super nerdy, but this seems totally doable. ;) >>>>>> >>>>>> >>>>>> >>>>>> I guess if you can rely on compiler's atomics support it's not too hard. >>>>>> Creating/managing threads is usually rather easy. >>>>>> >>>>>> // Johannes >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> fluid-dev mailing list >>>>>> fluid-dev@nongnu.org >>>>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>>>> >>>>>> >>>>> -- >>>>> Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity. >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something’s wrong. >> http://kirbyfan64.github.io/ >> >> >> _______________________________________________ >> 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
