Hardcoded Windows DLL dependencies about blizzardry HOT 3 OPEN

Ah good point! When Peter and I looked at this, only Node 0.10 and 0.12 were relevant. Is there any way to dynamically fetch the DLL-name based on node-gyp?

from blizzardry.

Or at least, if I remember correctly, the version Node was compiled with needs to match the version the libraries get compiled with.

from blizzardry.

I'm afraid it doesn't matter what Node or node-gyp uses.

Right now (however this could change if more file formats are added and so on), the only thing that matters is that the runtime DLL specified in c-lib matches the runtime linked with libblp (because fopen is used as an argument to blp_processFile).

Honestly I don't know how to make this generic. At least, after version 14.0 (VS 2015), the runtime library filename is no longer versioned (there's no msvcr140), only ucrtbase(d).

from blizzardry.