Re: [fluid-dev] I removed GLIB dependency from my build.

[Ceresa Jean-Jacques]

Hi,

 

>Tom: Would this really make the Windows users life easier as originally intended by the glib removal?

Removing glib in Windows is benefict only because the glib dlls is very large compared to the size of the FluidSynth library.

The effective code in glib necessary to Fluidsynth (mutex,event, atomic, thread,logging) is very small. It is so small that writting an equivalent

substitute code using native OS API become easy. So glib seems only valuable for large application.

 

As reported by Element (http://lists.nongnu.org/archive/html/fluid-dev/2017-09/msg00022.html):

The main advantage of glib is the very important concept of portability that make fluidsynth easly maintainable (and unmaintenable without this concept).

The true disadvantage of glib make fluidsynth library unusable in very small imbedded application (fanless rack of synthesizer,...).

 

>Tom:I actually forgot the fact that C11 programs should be compilable in VS using llvm-clang.

Keeping simplicity, i think is a good opinion to forget this. I don't know about C11, but i vote for the use of a custom minimum necessary library (static/dll) with an API compatible (glib or c11) ?

With the help of Element knowledge about glib, this should be feasable.

cheers.

jjc

> Message du 11/10/17 13:12
> De : "Tom M." <address@hidden>
> A : address@hidden, "FluidSynth mailing list" <address@hidden>
> Copie à :
> Objet : Re: [fluid-dev] I removed GLIB dependency from my build.
>
>

> Any solution staying with Visual Studio would be highly appreciated.
>
>

Agreed. I actually forgot the fact that C11 programs should be compilable in VS using llvm-clang. Not sure if this is an option, never tested myself.
>
>
>

Tom
>

>

>

2017-10-11 12:45 GMT+02:00 Reinhold Hoffmann <address@hidden>:
>

Hi,

 

Many of the Windows users use Visual Studio (good or bad).

Any solution staying with Visual Studio would be highly appreciated.

 

Reinhold  

>

---

Von: fluid-dev [mailto:fluid-dev-bounces+reinhold=address@hidden] Im Auftrag von Tom M.
> Gesendet: Mittwoch, 11. Oktober 2017 10:19
> An: FluidSynth mailing list
> Betreff: Re: [fluid-dev] I removed GLIB dependency from my build.
>
>

 

TinyCThread looks good. Even though they only support Win32 and Pthreads they implement the C11 API. So we could move to C11:
>
>

#ifdef __STDC_NO_ATOMICS__
>

  #error "Compiler has no C11 atomics"
>

#endif
>
>

#ifdef __STDC_NO_THREADS__
>

  #include <tinycthread.h>
>

#else
>

  #include <threads.h>
>

#endif
>
>

This however might be the end of OS/2 support. Compiling on Win32 only with MinGW or CygWin. Would this really make the Windows users life easier as originally intended by the glib removal?
>
>
>

Tom
>

>

>

2017-10-10 23:54 GMT+02:00 Ryan Gonzalez <address@hidden>:
>

FWIW I had been working on removing glib two years ago or a bit less
> (dang, was it really that long ago?), as this is basically why I
> stopped when I was almost done: it really wasn't maintainable.
>
> Realistically, I do think there's literally no major alternative. I
> mean, for atomics there's libatomic_ops:
>
> https://github.com/ivmai/libatomic_ops
>
> which was built for and is still used by the Boehm GC. If Windows is
> the only barrier to C11 adoption, maybe TinyCThread could fill in for
> the mean time? https://tinycthread.github.io/
>

> On Tue, Oct 10, 2017 at 12:25 PM, Tom M. <address@hidden> wrote:
> > Without having seen your changes, you have probably done something like what
> > existed before glib:
> > https://github.com/FluidSynth/fluidsynth/blob/b49458e817ed09aedd948a6ea1831965373adc80/fluidsynth/src/fluid_sys.h#L142
> >
> > This is not an option because it's unmaintainable. See the related
> > discussion here for possible solutions:
> > http://lists.nongnu.org/archive/html/fluid-dev/2017-09/msg00031.html
> >
> >
> > Tom
> >
> >
> > 2017-10-10 18:57 GMT+02:00 Carlo Bramini <address@hidden>:
> >>
> >> Hello,
> >> as I wrote in the subject, I worked a bit on Fluidsynth and I made a
> >> version that works fine without external dependencies. I compiled it on the
> >> ancient VisualStudio 6.0 and my version currentl runs on Windows.
> >> However, it should not be difficult to include a new driver for adding
> >> again support to GLIB at compile time or to add support for other platforms,
> >> especially direct pthreads support.
> >> I'm wondering if you would be interested to evaluate these changes and how
> >> to do it if it could be possible to add them to the original source code.
> >> I have still some work to do on it, because some functions are still not
> >> implemented and my coding started almost from version 1.1.7 (I cloned the
> >> repository a bit before the release of the latest stable) but in the
> >> meanwhile new patches have been submitted, so I should also align my code at
> >> latest revision.
> >>
> >> Sincerely.
> >>
> >> _______________________________________________
> >> fluid-dev mailing list
> >> address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/fluid-dev
> >
> >
> >
> > _______________________________________________
> > fluid-dev mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/fluid-dev
> >
>
>
>
>

--
> Ryan (ライアン)
> Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
> https://refi64.com/
>

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

>

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

>

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