> One solution would be to link additionally with fltk.lib, so > that the same > applies as with our FLTK project test programs: they pull > WinMain() from > the static lib. I don't know whether this is good style, > however, since it > could come to ambiguities...
I can't vouch for the MS linker, but with the gcc linker, that ought to be OK - it will pick the symbols from the DLL first (if we ensure it is listed first) and then will only pick any remaining unresolved symbols from the static lib; which should only be WinMain() as all the other symbols ought to be in the DLL, I think. So... This might well be the easy option... I have never had problems with the DLL and mingw (Though I do not use it all that much now.) Have I just been lucky, or is it actually different in this respect? 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-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
