[Openicc] [argyllcms] Re: CC Profiles In X Specification and dispwin

[Frédéric Crozat]

On Jan 15, 2008 5:53 PM, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> Am 15.01.08, 16:54 +0100 schrieb Frédéric Crozat:
>
> > On Jan 15, 2008 3:30 PM, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> > > > > The Oyranos library should build even with a non installed FLTK. But
> > > > > I'd take your suggestion for RPM packaging and will provide something like
> > > > > oyranos-ui.
> > > >
> > > > For the record, it is not only for packaging, but for better
> > > > acceptance by other projects. I'm not
> > > > sure KDE (or GNOME) guys would be happy to have to install FLTK just
> > > > to build one of their software :)
> > >
> > > Good, I will check that tollkit dependent things are competely optional.
> >
> > If you want to do it "the right way" (IMO), you should definitely
> > distribute FLTK parts in a separate tarball.
> > As an added bonus, this will ensure you are only using public API.
> > Just modifying your module to put tooklit dependent stuff as optional
> > will cause a problem for distributions
> > which might  want to enable it (because it will add toolkit as build
> > dependencies).
>
> So far, I know what the GUI includes.
>
> If a distributor likes the GUI, the dependency to build comes anyway.
> Actually I dont see a conflict. Is it a problem for automated builds?

It is a bootstrapping problems :

if you want to bootstrap all packages for an application which rely on
Oyranos (and not on FLTK)
but these packages have enabled UI part because distribution might
ship them in a separate sub package,
you will need FLTK in the bootstrapping process, even if you don't
need it at all.

-- 
Frederic Crozat