[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 2/2] Use GLib allocation in the audio subsystem.
From: |
Steve Holmes |
Subject: |
[PATCH 2/2] Use GLib allocation in the audio subsystem. |
Date: |
Wed, 6 Oct 2010 11:45:33 -0700 |
I am confused by this thread now. I see GLib and glib spoken of as
separate and opposite intities are they indeed two different
libraries? Also, I thought Chris was submitting patches to standardize
memory allocation routines to use g_alloc or something similar.
Wouldn't those routines rely on one of the GLib or glib libraries?
Can someone help clear the fog out of my head? <smile>
On Tue, Oct 05, 2010 at 03:39:11PM +0200, Boris Dusek wrote:
> Hello Andrei,
>
> On Oct 4, 2010, at 12:05 PM, Andrei Kholodnyi wrote:
>
> >> I will look at the things where we use GLib and try implementing
> >> the small(er) things.
> >
> > I have a question.
> > Do you plan to remove GLib, if yes, then why.
> > The reason I'm asking it was planned to switch to gmainloop,
> > now, if it is still the case, why do you need to replace glib calls.
>
> thanks for your question. It's a good one and I have been thinking about it
> myself in the last 2 days.
>
> My motivation to remove glib is that it is a big dependency on non-FreeDesktop
> platforms. E.g. on Mac OS X, it's 1.0 MB (with single architecture) that I
> would have to compile and redistribute with Speech Dispatcher. Whole Speech
> Dispatcher itself is like 0.5 MB at most.
>
> I thought of different options: reimplementing most GLib stuff we use in
> libcommon, reimplementing all GLib stuff we use in libcommon, and using C++
> standard library. But in a situation which you pointed out (where we are
> looking forward to extend usage of GLib for more important things like
> mainloop, DBus etc., so GLib is here to stay), all these options start to seem
> as redundant work. Also what this would lead to would be touching working code
> and requiring people to change their habits (e.g. using spd_free instead of
> g_free etc.).
>
> I also considered as an important reason that FreeDesktop platform is an
> absolute priority for Speech Dispatcher, and non-FreeDesktop platforms are
> nice-to-have, but not priority, platforms.
>
> So to sum up, I think that while having some negatives, when I consider all
> things, then to go with glib is a reasonable way to go with the current
> codebase of Speech Dispatcher.
>
> Best regards,
> Boris
> _______________________________________________
> Speechd mailing list
> Speechd at lists.freebsoft.org
> http://lists.freebsoft.org/mailman/listinfo/speechd
- [PATCH 2/2] Use GLib allocation in the audio subsystem., (continued)
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Christopher Brannon, 2010/10/02
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Boris Dusek, 2010/10/03
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Andrei Kholodnyi, 2010/10/04
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Hynek Hanke, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Halim Sahin, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Rui Batista, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Christopher Brannon, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Bohdan R . Rau, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Halim Sahin, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Boris Dusek, 2010/10/05
- [PATCH 2/2] Use GLib allocation in the audio subsystem.,
Steve Holmes <=
- [PATCH 2/2] Use GLib allocation in the audio subsystem., Christopher Brannon, 2010/10/06