On Tue, Oct 31, 2006 at 10:56:43AM +0100, Bastiaan Jacques wrote: > On Tue, 2006-10-31 at 09:26 +0100, strk wrote: > > Sorry for the question, but I'm very confused about the topic, > > That's definitely not something you should be apologising for. > > > and the autoconf scripts seems as confused as me. > > So what *is* klash ? Is it the plugin ? Or is it the standalone > > executable using KDE GUI ? > > Klash consists of two things: > > 1) the KDE gui executable gui/klash > 2) the klash kpart plugin, also built in gui/. > > I believe it is currently not possible to build either one (assuming > there have been no recent changes to the build system to the opposite > effect): they must always be built in pairs.
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). 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) > That said, we have to decide on the naming system for Gui executables (a > few proposals were mentioned in an earlier thread I started). 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 ? --strk; _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
