Sorry for the delay in replying.
There's not much that needs to be done, as long as the code isn't writing to the registry or anything like that.
In the same places as they are now:
(Note: /home is an alias which resolves to the Opus program folder, usually C:\Program Files\GPSoftware\Directory Opus.)
- On 64-bit HDD installs:
x64 DLLs go in /home/Viewers
x86 DLLs go in /home/x86/Viewers
- On 32-bit HDD installs:
x86 DLLs go in /home/Viewers
x64 DLLs go in /home/x64/Viewers (This is new in Opus 11.12.5 and above.)[/li][/ul]
The HDD installs have copies of the other "bitness" so that they can export either or both to USB. (Priori to 11.12.5, only 64-bit installs had this capability. Now 32-bit ones do as well.)
Copying the plugin DLLs to USB sticks is done for you by Opus. Plugins do not need to worry about that. Opus will copy the appropriate DLLs to the appropriate place on the USB stick automatically.
The only extra thing you need to do is tell Opus that SciLexer.dll also needs to be copied, since Opus wouldn't know that extra DLL is part of your plugin otherwise. To do that, you just need to add it to the usbsafe.xml manifest details. The j2k plugin is an example that does this for two extra files. Here is its usbsafe.xml manifest:
As you can see, it just specifies a filename, so the additional files should be in the same folder as the plugin itself.
If you have extra DLLs or other files whose names are different on x86 and x64, the manifest can handle that as well. Here's how the Archives plugin deals with unrar.dll and unrar64.dll:
[quote]And how to copy config file?
/dopusdata/dosv.config.xml
[/quote]
Config files should be in the folder you get back from the GetConfigPath helper function. (Usually /dopusdata/ConfigFiles/Plugins.) As long as they are in there, they will be exported automatically.
Officially, the /dopusdata/Logs dir is private and it wasn't envisaged that plugins would write to there, so putting your own files in there may confuse some part of Opus (although it may be fine as well, I am not sure).
As far as USB installs go, it's the same on them as for an HDD install, as long as you are obtaining the config path via the helper API, or by asking Opus to resolve the /dopusdata alias. i.e. As long as you are not assuming the config folder is in the user's profile folder. (USB installs should not modify the user profile folder, since all the Opus config folders will be in another location in that scenario.)
I can try. I'm not sure what the question is, sorry. Do you need a way to map from a filename/extension to a file type?