Remove glib dependency?

[MrSapps]

I am trying to use fluidsynth in a game engine. There exists "lite" versions that remove glib which makes it very simple to build, however these version are extremely old (1.1.6 era).

Would it ever be considered to have an option to build without depending on glib? Even if its a subset of the whole lib functionality?

[derselbst]

In your post I'm missing arguments explaining why you want to remove glib.

Would it ever be considered to have an option to build without depending on glib?

See #847.

Even if its a subset of the whole lib functionality?

Unlikely. I will not cripple the library.

[sykhro]

Xbox 1, Playstation 1/2/3 and ESP MCU probably others.

Realistically those can never be supported due to proprietary SDKs (or obscure homebrew toolchains). Besides, you'd still need to write an audio driver for each of them, which is no small feat compared to the little editing needed as of now to (hackily) swap out GLib

[derselbst]

I don't understand why allowing the glib layer to be swapped out is "crippling" the library then?

You initially said: "Even if its a subset of the whole lib functionality?" in connection with "have an option to build without depending on glib" Since glib is used by fluidsynth's core functionality, I replied with "crippling".

Xbox 1, Playstation 1/2/3 and ESP MCU probably others.

Not to forget Nintendo, Sega, Amiga and C64... Sorry, I cannot take this seriously.

But allowing glib to be easily switched out can't hurt maintaince?

Have you ever looked at the code? The whole glib stuff is located in three files: fluid_sys.c, fluid_sys.h and fluidsynth_priv.h . So what exactly are you complaining about?

[MrSapps]

Xbox 1, Playstation 1/2/3 and ESP MCU probably others.

Realistically those can never be supported due to proprietary SDKs (or obscure homebrew toolchains). Besides, you'd still need to write an audio driver for each of them, which is no small feat compared to the little editing needed as of now to (hackily) swap out GLib

fluid_synth_write_s16 is enough to make it work on Xbox1, PS2 and 3, PS1 needs a lot more edits so I probably shouldn't have mentioned that one.

I don't understand why allowing the glib layer to be swapped out is "crippling" the library then?

You initially said: "Even if its a subset of the whole lib functionality?" in connection with "have an option to build without depending on glib" Since glib is used by fluidsynth's core functionality, I replied with "crippling".

It usually implies removing functionality which wouldn't have been the case, so I was confused by that statement.

Xbox 1, Playstation 1/2/3 and ESP MCU probably others.

Not to forget Nintendo, Sega, Amiga and C64... Sorry, I cannot take this seriously.

Why can't you take this seriously? If Windows9X is supported the NT kernel in Xbox 1 years newer and the hardware is much more powerful than PC's of the Win9x era.

But allowing glib to be easily switched out can't hurt maintaince?

Have you ever looked at the code? The whole glib stuff is located in three files: fluid_sys.c, fluid_sys.h and fluidsynth_priv.h . So what exactly are you complaining about?

I will try getting it to use Windows OS calls and let you know how it goes. If there is some easy edits that makes this easier would they be accepted in a PR?

[derselbst]

Xbox 1, Playstation 1/2/3 and ESP MCU probably others.

Not to forget Nintendo, Sega, Amiga and C64... Sorry, I cannot take this seriously.

Why can't you take this seriously?

Because it appears to me that you were just listing proprietary platforms where glib (and no other free, open, portable OSAL) is supported.

If there is some easy edits that makes this easier would they be accepted in a PR?

Most likely yes.

[MrSapps]

I've added a PR here that pushes all of the glib calls into the priv header etc #901 with this I can add glib_replacement.h in my fork and have it build without using glib