mcs manager build error
fourdan at xfce.org
Tue Oct 21 07:26:59 CEST 2003
The mcs manager is based on GModule, so is the plugin mechanism in the
On Tue, 2003-10-21 at 03:35, edscott wilson garcia wrote:
> On Mon, 2003-10-20 at 15:20, Benedikt Meurer wrote:
> > On Mon, 20, Oct 2003, edscott wilson garcia wrote:
> > > > I don't think libxfcegui4 should depend on dbh...
> > >
> > > Me neither: the dependency makes everything else depend on dbh, which is
> > > unnecessary. That's why I reverted the changes. Now I've put the combo
> > > object into libxffm_combo.so. So for xfrun4 history, if xffm is
> > > installed, it will link to this library and share history information
> > > with xffm. If xffm is not installed, it will just fallback to current
> > > code.
> > >
> > Just an idea: But from my POV it makes most sense to do this check at
> > runtime (the check for libxffm_combo.so) in xfrun4, so a user can
> > decide to install/uninstall xffm without affecting xfrun4 regardless
> > of whether it was compiled with or without history support. This
> > should be an easy task using GModule.
> That sounds very good. Could you provide some simple example code to
> illustrate the use of GModule? I'm a bit illiterate in GModule and some
> models to follow would save much time in development and be much
> > > regards,
> > > Edscott
> > regards,
> > Benedikt
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
Olivier Fourdan - fourdan at xfce.org
Interoperability is the keyword, uniformity is a dead end.
More information about the Xfce4-dev