Greg Ercolano wrote:
>       Albrecht: I think VS releases *two* libs: fltkdll.lib and fltkdll.dll
>       (Note one ends in .lib, the other in .dll)
> [..]
>       Hmm, I wonder if we broke something in the VS build flags recently
>       for fltkdll.
> [..]
>       Perhaps [..] the generation of fltkdll.lib needs FL_DLL /undefined/
>       so that WinMain() gets defined in it.
> [..]
>       [I'll] sniff around to see if I can figure out how the two 
> fltkdll.{lib,dll}
>       files are generated.

   I'm guessing the design intention was that an app wanting FLTK dlls
   would /statically/ link to fltkdll.lib (?) which defines WinMain() (?)
   but does not include the binaries of the lib itself (?), and /it/ handles
   dynamically loading the fltk dll lib at runtime..?

   I tried to figure out how fltkdll.lib is generated, but couldn't:

   I loaded fltk in VS2010 and looked at the properties for the fltkdll project,
   but could not understand how fltkdll.lib gets generated. The creation of the
   *dll.dll seemed clear enough, but not the *dll.lib.

   I resorted to grepping the ide/visual2010 dir for fltklib.dll, but
   only found imports, not output.

   I defer to the MS/VS experts on how this is all supposed to work.
   Spending too much time in VS makes me rage.

   Matt or Mike or Bill: do you guys remember how this is all supposed
   to work?
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to