Quote:
Originally Posted by Derek Sapfe
Somehow Reaper can't read the libcurl.dll from the plugin's directory?
|
In Reaper, plugin dlls will unfortunately end up searching linked dlls in the directory where reaper.exe itself is located. While you could use that for testing yourself, you obviously can't make a released product behave that way.
Some options :
1) Load the libcurl.dll dynamically in your plugin with LoadLibrary, GetProcAddress etc instead of using the dll loading .lib file. Painful if you need to use lots of functions from the dll. Note that a relative path to the libcurl.dll is likely not going to work, you will need to form the full absolute path to the dll to be sure LoadLibrary will be able to find it.
2) Install the libcurl.dll in the Windows system directories. Quite nasty. I would personally hate a plugin that did that.
3) Investigate if there's any way to just compile the libcurl source code directly into your plugin or statically link into it.
4) Use something else than libcurl. WDL contains some network access stuff. (jnetlib)
I would probably go with option 4 myself, I strongly dislike libraries that force having to use them via dlls on Windows. (Or make it very hard to use them in any other way.)