On 22/12/10 14:53, Albrecht Schlosser wrote: > Then I must conclude that the comment in FL/Fl_Export.H is ... well, > let's say... not precise and should be changed to say that this is > only needed "when using the MS development tools" ? > > /* > * The following is only used when building DLLs under WIN32... > */
I am not sure - I always just assumed it was used by all Windows compilers... If you do a configure --shared in a Msys/mingw build, it generates the DLL's, albeit leavingthem in the src dir which I find annoying, and names them like "mgwfltknox*.dll" or some such (not on a Windows machine now...) so it is clear the DLL's are not MSVC compatible from the name > Yep, I know. That's why I don't have experience with building FLTK as > a dll ;-) -- but I did with other plain C code, and I managed to build > a dll with Cygwin/MinGW that is used in an application created with > MS tools (AFAICT, at least it was some years ago. I don't know what > they are doing today, but my dll is still working - "they" are calling > functions from my dll). Yes - plain-C is less problematic and the DLL's are pretty much interchangeable. But C++ DLL's won't play well. We have a supplier that persists in providing us with C++ DLL's compiled with VC6. We then write a small VC6 wrapper DLL that calls these DLL's but exposes C-API versions of the methods we actually use, which we then call from mingw. Not the most elegant solution, but it works OK. Just calling the VC6 DLL's of course does not work! _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
