Re: NSIS packaging for custom plugins

[Christopher Maynard <Christopher.Maynard () gtech com>]

Michael Lum <michael.lum@...> writes:

> I don't know how the NSIS packaging works but when you want to add a custom 
> plugin it looks like you need to modify both
>
> Custom.nmake and custom_plugins.txt
>  
> Is this correct?

Yes.  Custom.nmake adds the custom plugins to Makefile.nmake's PLUGINS via
the CUSTOM_PLUGINS and custom_plugins.txt adds the custom plugins to
wireshark.nsi's SecPlugins.

> If so would it be possible to just have Custom.nmake and generate the other 
> file (if its required)?

I don't think this could be done since the formats are different:

Custom.nmake:
    ../../plugins/foo.dll

vs.

custom_plugins.txt:
    File "${STAGING_DIR}\plugins\${VERSION}\foo.dll"




___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe