[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re[2]: [Gnash-dev] multiple GUIs
From: |
Martin Guy |
Subject: |
Re: Re[2]: [Gnash-dev] multiple GUIs |
Date: |
Thu, 19 Oct 2006 13:06:49 +0100 |
2006/10/16, Udo Giacomozzi <address@hidden>:
Monday, October 16, 2006, 3:09:51 PM, strk wrote:
s> I'd name them gtk-gnash, sdl-gnash, fb-gnash etc. etc.
"gnash-gtk", "gnash-sdl", ...?)
That's what I have been using for testing,
with configure --no-shared --enable-wotsit=whatever --program-suffix=-whatever
(static is necessary otherwise the replacement libraries break the
existing binaries). FOr developer testing that is sufficient.
BTW, gtk-gnash is ambiguous (what *renderer* is that?).
--program-suffix=-cairo-sdl where there are more than one divergence
from the defaults
If we want to support choice of gui/renderer/mp3-renderer at runtime
that would be splendid, the same as mplayer and friends do. In fact
that would be cleanest, with a choice of interfaces to include at
build time and with the available choices displayed by --help or by
--gui=list
That would also force a clean internal interface between the
different modules and get rid of the nested Ifdefs and multiple
executables that happen at present.
Maybe it is too late to kill off the name "klash" but mapping it
internally into "gnash --gui=kde" by inspecting argv[0] or by the fact
that the klash executable is built with a single gui is ok though.
M
- [Gnash-dev] multiple GUIs, Bastiaan Jacques, 2006/10/16
- Re: Re[2]: [Gnash-dev] multiple GUIs,
Martin Guy <=
- Re[4]: [Gnash-dev] multiple GUIs, Udo Giacomozzi, 2006/10/19
- Re: [Gnash-dev] multiple GUIs, strk, 2006/10/19
- Re: [Gnash-dev] multiple GUIs, Martin Guy, 2006/10/19
- Re: [Gnash-dev] multiple GUIs, Rob Savoye, 2006/10/19
- Re: Re[2]: [Gnash-dev] multiple GUIs, Tomas Groth, 2006/10/19
Re: [Gnash-dev] multiple GUIs, Rob Savoye, 2006/10/16
[Gnash-dev] Re: multiple GUIs, Stefan Schweizer, 2006/10/16