Hardlinks and DLLs

Asked Jul 18 '16 at 20:50

Active Jul 18 '16 at 21:11

Viewed 45 times

I have a shared DLL that I would like to expose as multiple different DLLs with different names in different directories. I figured using hardlinks would work and that running each one would be a different memory space, but from testing it out, it seems to load the shared DLL rather than each hard linked DLL. Furthermore, loading multiple hard linked DLL will just go back to the one that was already loaded/

Does anyone have any suggestions to go around this memory sharing of the hard linked DLLs so that each one will have their own memory?

Note that I don't want to make multiple copies of the DLL because of space constraints.

edited Jul 18 '16 at 21:11

asked Jul 18 '16 at 20:50

stealthyninja

Why not copy it? That will be more reliable, by far. – MSalters Jul 18 '16 at 20:53
@MSalters Space restriction, we want to keep the overall size of everything as small as possible – stealthyninja Jul 18 '16 at 21:10

Hardlinks and DLLs

0 Answers0