On Tue, Oct 31, 2006 at 11:43:53AM +0100, Bastiaan Jacques wrote: > On Tue, 2006-10-31 at 11:24 +0100, strk wrote: > > Ok, so it *was* correct to have a check in ./configure.ac aborting > > if anyone attempts to build klash *plugin* with non-kde *gui*, right ? > > (that check is now commented out). > > No, if the build system allows us to build both the KDE Gui and another > Gui, that should be fine.
Do you mean that libgnashgui.so can currently have support for multiple GUIs ? > > Also, it is *wrong* defining USE_GUI_KDE iff either kde gui was requested > > *or* klash was enabled, right ? (this is currently what ./configure does, > > possibly ending up with two enabled GUIs) > > Actually, I think that might work, although I have not tested such a > combination. We certainly want to be able to do that. If we plan to allow for multiple GUIs in libgnashgui (and libgnashplayer) we should change the --enable-gui switch to accept a comma-separated list of guis, and update interface of Player to allow setting a specific GUI for use. > > IIRC last words were for a plugin architecture. In 0.7.2 this will > > surely NOT happen, so we have to find a compromise. > > The question is: do we want to enable building *both* klash *and* > > a !KDE gui'd gnash for 0.7.2 ? > > Yes. The important thing is that when Klash is enabled, the KDE GUI is > built (in addition to whatever GUI the user specifies). I have no way to test this currently, as the kde.m4 macro is broken (at least on my system) in that it doesn't recognize availability of the required headerfiles. --strk; _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
