> 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 ?
I really don't know what is best, and I haven't looked at the details of the implementation at all, so I've no idea how practical (or otherwise) my suggestions are. I guess I'd envisaged a "libfltk_cairo" type approach, so I could build fltk with --enable-cairo set, but then choose to pull in "libfltk_cairo" (and cairo/pixman) only for projects that need it... At present, I need to link Cairo into everything if I configure fltk with --enable-cairo set. This all assumes, of course, that fltk itself is not rendered with Cairo - that would be a whole other thing...! SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
