Wireshark-dev: Re: [Wireshark-dev] NSIS packaging for custom plugins
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Christopher Maynard <Christopher.Maynard@xxxxxxxxx>
Date: Wed, 18 Dec 2013 20:00:01 +0000 (UTC)
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"