Re: [Wireshark-dev] Adding install target to Makefile.nmake

2013-11-13 Thread John Dill
>Message: 4 > Date: Wed, 13 Nov 2013 13:44:15 -0500 > From: "John Dill" > To: > Subject: Re: [Wireshark-dev] Adding install target to Makefile.nmake > Message-ID: > > > > Content-Type: text/plain; charset="iso-8859-1" > &g

Re: [Wireshark-dev] Adding install target to Makefile.nmake

2013-11-13 Thread John Dill
>Message: 3 > Date: Wed, 13 Nov 2013 16:12:09 + > From: Graham Bloice > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Adding install target to Makefile.nmake > for plugins > Message-ID: > > Content-Type: text/plain;

Re: [Wireshark-dev] Adding install target to Makefile.nmake for plugins

2013-11-13 Thread Sreejith M M
If we just build a plugin, i dont think the dll gets copied to the plugin install directory. In that way, the solution provided by OP helps On Nov 13, 2013 9:43 PM, "Graham Bloice" wrote: > On 13 November 2013 16:01, John Dill wrote: > >> >> I added an install target for my protocol dissector pl

Re: [Wireshark-dev] Adding install target to Makefile.nmake for plugins

2013-11-13 Thread Graham Bloice
On 13 November 2013 16:01, John Dill wrote: > > I added an install target for my protocol dissector plugin nmake file. > Simplifies the tedious step of copying it to the Wireshark/plugins folder > during development and test. Here's the snippets that I added. > > > The nmake build already copie

[Wireshark-dev] Adding install target to Makefile.nmake for plugins

2013-11-13 Thread John Dill
I added an install target for my protocol dissector plugin nmake file. Simplifies the tedious step of copying it to the Wireshark/plugins folder during development and test. Here's the snippets that I added. --- INSTALL_ROOT=$(PROGRAMFILES)\Wireshark\plugins WIRESHARK_VER=1.10.3 !IF EXIST($(I