Asif, Now that there seems to be some light at the end of the DLL tunnel, can I ask again if you even need the DLL linkage at all?
I know you were keen to get the resource saving that using the DLL might bring - but is that really going to happen in your use case? For example, if we say the fltk DLL is about 1MB, then I had an app that was approx. 500kB static linked, and that reduced to about 300kB linked to the DLL, so I was only saving about 200kB per app instance. The point I'm making is that (in very simplified terms) I would need to have more than 5 app instances before the DLL would represent a "win" - and even then, depending on how the DLL was wired into RAM it might still be more resource expensive than the static linked case. And of course static linking avoid the famous MS DLL-hell problem, too... Got to be worth considering, I think. SELEX Galileo Ltd 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
