| |
| |
On Tuesday, 23 November 2021 at 05:49:25 UTC Phil wrote: For what it’s worth, under Virtual Studio, I can only statically link any library into the final application. Although I access FLTK methods in my own library, they can only be linked when I bring all the .libs together in the application.
OK... I'm guessing that "Virtual Studio" is a typo. for "Visual Studio" here, so we are talking about Win32 dev...?
So, anyway, if you have built the fltk DLL's with VS, they should then Just Work, and dynamic linking should be fine - it's not my preferred approach, personally, but I have used it on Windows with both the VS and the mingw toolchains and it works OK. (Though you can not mix'n'match VS and mingw libs, they disagree with each other!)
That said, figuring out *how* to do DLL builds etc. with VS I always find challenging - I have never got along with VS, and I've been trying to use it, on and off, since it was called MSVC...
What are you trying, what works, what doesn't, etc....?
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/ed311b12-f838-4775-a77d-77e26061d6ffn%40googlegroups.com.
[ Direct Link to Message ] | |
|
| |
