Quote:
Originally Posted by stax76
Hello Myrsloik, I've some questions...
Is there some documentation or sample code for DLL discovery and loading?
Do all setup variants add VS to the Path env var and apps can rely on that?
Do all setup variants register the VS location in the registry? If so which key(s)?
I believe Load-Time Dynamic Linking is possible and preferred, I'm mostly unsure about path discovery.
|
Is there some documentation or sample code for DLL discovery and loading?
No. You read the location you need from the registry. HKLM/HKCU (depends on current user install mode) and then software\vapoursynth (or vapoursynth-32 for poor people) and the keys of interest are called VSScriptDLL and VapourSynthDLL. Simply use loadlibrary and call vsscript_getVSApi2() or getVapourSynthAPI() depending on which dll you use.
Do all setup variants add VS to the Path env var and apps can rely on that?
No. It's a user option and you can never depend on this.
Do all setup variants register the VS location in the registry? If so which key(s)?
Yes, see above. I guess portable doesn't but that's hardly a setup variant...