How to add plugin for nsis package?
See original GitHub issue- Version: 19.49.2
- Target: I want to use a plugin: http://nsis.sourceforge.net/ExecDos_plug-in.
My step:
- I download the plugin zip
- unzip and got “Plugins” dir
- I copy the “Plugins” dir to my custom include file location dir
- In my custom include file, I add
!addplugindir '.\Plugins'
- use Exec-dosc::exec.
- throw Error:
Plugin not found, cannot call ExecDos::exec
so, how to add plugin correctly?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Talk:How can I install a plugin? - NSIS Wiki
I needed to install "Dialogs" plugin, which is not included in NSIS distribution; Installation information is missing in the plugin's "readme.
Read more >New to NSIS, Installing a plugin - NSIS Forums
In the Inetc package you get 3 folders - \Contrib, \Plugins, and \Unicode. I've left the Unicode one there, and copied the Contrib...
Read more >How to add a DLL Plugin without NSH file into my NSIS script?
Plugin I'm trying to use is HwInfo plug-in (Official Link). The ZIP file comes with some source codes and a DLL file. I...
Read more >NSIS Plug-ins - Visual Studio Marketplace
Visual Studio Code 1.7 (and higher) will automatically install the NSIS extension as dependency. If you're using an older version, ...
Read more >How to use InstallOptions plugin in NSIS - YouTube
The code used in the video is ; Let's start by creating new nsis script … Show more. Show more. Show less. Comments....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@develar First of all, this shouldn’t be closed because it doesn’t work. There are multiple issues opened and I’m not sure why no one is trying to fix them.
So, can you please make an optional flag somewhere in the yml file where we can provide a custom path in which we can keep plugins, includes etc? Would really appreciate the answer on this one and I’m sure, many other people.
Works for me. use
!addplugindir ${PROJECT_DIR}\installer\plugins
, and put plugin into directory${PROJECT_DIR}\installer\plugins
. You can changeinstaller\plugins
to any directory you want in project