Plugins that need External Dependencies

[acozz]

Is there a better way to use external dependencies in plugins that need them then the current way (putting them in the QCD App folder)?

What I'm looking for is either a way to:

1) Be able to load the dependency from within the plugin (so it would look for it in the plugin folder). I don't know enough about dll's to know if this is possible in code.

or

2) The installer to be updated so you can install 2 different files to 2 different directories (maybe by combining two installers into one).

Are either of these possible?

[shaohao]

for 1:
You can use opGetPluginFolder to get the plug-in folder. Then use Win32 function--"LoadLibrary()" to load your external dlls. But this would be very complex for your plug-in dev. 'cause you must get all of the function address you need first. I have a better methord: You can set windows's path and add QCD's plug-in path into it.

for 2:
I've write a nsin script for creating QCD plug-in which you can add your own files. But you need nsis installed.

See attachment:

[Paul]

I would like to collect useful NSIS scripts to put in the DevZone for others to package their plugins with. If anyone has general scripts, or knows of common ideas that should be in an NSIS script, let's hear it.