[Wireshark-dev] plugin_if menu problems

2015-11-26 Thread Paul Offord
Hi, I am experimenting with the plugin_if menu functions. I'm creating the code in VS2013 and I have two stubborn errors that I can't seem to resolve. The code is: #include extern int proto_tmsvc; void menu_setup() { ext_menu_t * ext_menu, *os_menu = NULL; ext_menu =

Re: [Wireshark-dev] wiretap - using as a library rather than coupled with Wireshark?

2015-11-26 Thread Guy Harris
On Nov 25, 2015, at 9:30 PM, Richard Kinder wrote: > I’m looking at making a small tool to translate .pkt files (Wildpackets, > specifically the wireless traces) to pcap/pcapng format on the command line, > and it seems wiretap is one of the few options available

Re: [Wireshark-dev] wiretap - using as a library rather than coupled with Wireshark?

2015-11-26 Thread Richard Kinder
Thanks a lot for the pointers Guy. Let me dig a little deeper into the code. -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Guy Harris Sent: Thursday, 26 November 2015 7:41 PM To: Developer support list for Wireshark

Re: [Wireshark-dev] wiretap - using as a library rather than coupled with Wireshark?

2015-11-26 Thread Dario Lombardo
On Thu, Nov 26, 2015 at 9:41 AM, Guy Harris wrote: > > It can't be, and probably will never be able to be, built independently of > the "Wireshark utilities" library, the source to which is in the wsutil > directory. > Provided that this is not a published lib, that has an

Re: [Wireshark-dev] Automated RPM-based-Linux build setup? (was Re: Automated Windows build setup? (Chocolatey?))

2015-11-26 Thread Peter Wu
On Wed, Nov 25, 2015 at 02:51:18PM -0800, Guy Harris wrote: > > On Nov 25, 2015, at 2:44 PM, Guy Harris wrote: > > > On Nov 25, 2015, at 11:01 AM, Peter Wu wrote: > > > >> Has there been any progress/work on an automated Windows environment > >> setup?

[Wireshark-dev] README.plugins regarding menus incorrect?

2015-11-26 Thread Paul Offord
Hi, The notes in section 6 of README.plugins show examples of menu entries. An example is: ext_menubar_add_entry(ext_menu, "TestEntry2", "Test Entry 2", NULL, menu_cb, ); But using this example causes an IntelliSense error in VS indicating there are too many parameters. The

Re: [Wireshark-dev] README.plugins regarding menus incorrect?

2015-11-26 Thread Alexis La Goutte
On Thu, Nov 26, 2015 at 2:18 PM, Paul Offord wrote: > Hi, > > > > The notes in section 6 of README.plugins show examples of menu entries. > An example is: > > > > ext_menubar_add_entry(ext_menu, "TestEntry2", "Test Entry 2", > > NULL, menu_cb, ); > > > > But

Re: [Wireshark-dev] wiretap - using as a library rather than coupled with Wireshark?

2015-11-26 Thread Guy Harris
On Nov 26, 2015, at 1:18 AM, Dario Lombardo wrote: > Provided that this is not a published lib, that has an unstable interface, > that... whatever constraint you can figure out, I think that it could be used > "as-is". To achive that wouldn't be enough to add the

Re: [Wireshark-dev] plugin_if menu problems

2015-11-26 Thread Paul Offord
I can answer part of the problem myself. Adding #define WS_BUILD_DLL to the head of the file stops the dllimport issue. Best regards...Paul From: Paul Offord Sent: 26 November 2015 22:37 To: 'wireshark-dev@wireshark.org' Subject: plugin_if menu problems Hi, I am