Karandra

I'm not sure whether I should create a new issues for this or not, this place seems fine. I ran the PVS-Studio static analyzer on both v1.3 and v2.0 branches....

Sorry but what is "IANAL"? My use case is the following. I statically link Dokany to my own DLL (also LGPL) and that DLL is used in the final product....

Unfortunately, static build will double (at best) the amount of VS build configurations. I'm not sure about including it in the installer. Static lib isn't needed by users installing Dokany...

Yeah. If anyone wants to link statically s/he probably knows what to change in VS options. Though it also could be documented as it's only two options (if you count...

There's one more thing I forgot about. The `_EXPORTING` macro constant which controls import/export specification and definition of `DOKANAPI` and `DOKAN_API` macros (why there are two of them?). This `_EXPORTING`...

Sorry, I'm idiot and couldn't find all places with `DokanInit` at once.

Now it has been built successfully.

Yeah, that would be better indeed. I'll make the changes. Could it be possible to implement such thing for v1.x? As far as I know there is no global Init/Shutdown...

> Or maybe not use global function pointers but function pointer attached to the instance. In the same fashion as operation callbacks? I'd like that solution.

I'll see what I can do. I still need to see has been changed between that version and the current one.