Re: [Wireshark-dev] Template for external dissector plugin

2011-12-21 Thread Jaap Keuter
On 2011-12-21 11:00, Reinhold Kainhofer wrote: > On 20/12/2011 17:12, Reinhold Kainhofer wrote: > >> On 20/12/2011 16:36, Jaap Keuter wrote: >> >>> Just for my information, is this the crux of your location independance? >>> >>> find_package(Wireshark) >>> include_directories (${WIRESHA

Re: [Wireshark-dev] Template for external dissector plugin

2011-12-21 Thread Reinhold Kainhofer
On 20/12/2011 17:12, Reinhold Kainhofer wrote: > On 20/12/2011 16:36, Jaap Keuter wrote: >> Just for my information, is this the crux of your location independance? >> >> find_package(Wireshark) >> include_directories (${WIRESHARK_INCLUDE_DIRS}) >> > Yes, the cmake/FindWireshark.cmake file (which i

Re: [Wireshark-dev] Template for external dissector plugin

2011-12-20 Thread Reinhold Kainhofer
On 20/12/2011 16:36, Jaap Keuter wrote: > Just for my information, is this the crux of your location independance? > > find_package(Wireshark) > include_directories (${WIRESHARK_INCLUDE_DIRS}) > Yes, the cmake/FindWireshark.cmake file (which is executed with the find_package) locates the libwiresha

Re: [Wireshark-dev] Template for external dissector plugin

2011-12-20 Thread Jaap Keuter
On 2011-12-19 16:37, Reinhold Kainhofer wrote: > Although most wireshark plugin tutorials tell you to develop > your plugin inside the wireshark source code, > it it possible to develop a plugin in a separate directory. > > I have created a simple template and a corresponding > makefile for c

[Wireshark-dev] Template for external dissector plugin

2011-12-19 Thread Reinhold Kainhofer
Although most wireshark plugin tutorials tell you to develop your plugin inside the wireshark source code, it it possible to develop a plugin in a separate directory. I have created a simple template and a corresponding makefile for cmake to develop a plugin in a separate, external directory, lin