Roman Kantor wrote:
>
> Greg Ercolano wrote:
>
>> Since FLTK's mandate is to keep tiny apps tiny, even if
>> statically linked, maybe there's a benefit to have big widgets
>> in a separate lib, so that libfltk.a remains "small".
>
> I think it can be a part of the static library: any self-regarding
> linker should not link to unused objects within the archive.
Yes, that's probably right.
I suppose even a static link should ignore the unused modules,
even when widgets derive from one another, or even when an
unused module contains static data.
> As for for consistency ... don't know.
If there's no good technical reason for it, then it probably
doesn't make sense to keep it separate.
It would only mean more emails about unresolved externals
because folks forgot to link this 'extras' lib..
So I guess there's probably no need for it.. nevermind!
I've probably even brought this up before, and just forgot
the resolution.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
