>
> If it can be compiled (and linked) w/o print support, this is IMHO
> good enough for now. I don't work with any embedded devices, but I
> assume that embedded devices would use static linking for their
> applications. If this is correct, then we don't need to bother making
> another lib (for that reason).
>
> However, if my assumption is wrong, then it might be useful to create
> a different lib for printing support. This one would obviously depend
> on libfltkimages (for image printing functions), but image support
> would not necessarily also need printing. The conclusion is to have
> both parts in different libs, so that someone who needs images but
> no printing can use a shared lib w/o printing support.
>
> So far my comments. Can you estimate how big (in KB) the printing
> functions (lib) would be?
>
> Albrecht
Here are the library sizes with/without PostScript printing support:
WIN32 __APPLE__
OS-printing + PostScript-printing 76 K 116 K
OS-printing only 28 K 36 K
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
