> > Fabien (et al) > > Is it intended that the "--enable-cairo" option means the generated code > always depends on Cairo? > > I had expected it would work like OpenGL does - if you use it, you need > to link it in, but if you aren't using it, you don't. > > But, what I find is that if I build fltk-1.3 with "--enable-cairo" set > at configure, then I have to link *everything* against Cairo, whether it > is using Cairo or not. This seems like a bug to me, probably. > > Cheers, > --=20 > Ian Well, the problem is that I needed to add cairo functions calls in fltk internals and thus, the lib you link against in that case would need cairo at least each time you link with fltk which must be quite often :)
There is a way to avoid that like adding a new cairo option in configure allowing or not fltk code instrumentation , even in that last case, we would need an fltkcairo lib module to make sure fltk lib is independent from cairo. Could be done if fltk internal cairo calls related functionality are disabled, any thoughts ? Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
