Wireshark-dev: Re: [Wireshark-dev] Is there a way to change the path (location) of wireshark PL
From: yenan <[email protected]>
Date: Thu, 10 Apr 2008 04:30:48 +0000
Thank you much for the reply!I really appreciate that!
 
My main concern is, I am willing to build a wireshark plugin dissector outside of wireshark directory, in Linux.
For example, my wireshark source code is in $home/wireshark/ , but want to include the plugin in $home/plugin/ which is independant from wireshark directory, can I use the configure option:--with-plugins[=DIR] , to achieve my goal? If yes ,is there any modification needed to top level Makefile and configure.in ?
 
 Can you please give me a simeple example of this option, since I have tried a whole without any achievement... The build keep looking for plugins in /wireshark/plugins/ directory... :(
 
 
> By putting the plugin into $HOME/.wireshark/plugins, or the Windows
> equivalent, which is the "personal" plugin directory.
>
> The only directories in which Wireshark will look for plugins are the
> "system" plugin directory and the "personal" plugin directory.
 
System plugin =  plugin install in wireshark/plugin, personalplugin directory =  $HOME/.wireshark/plugins, is that what you mean?
 
Thank you for your help!!!
 
Regards
Nan
 
 
 


> Date: Wed, 9 Apr 2008 18:26:02 -0700
> From: [email protected]
> To: [email protected]
> Subject: Re: [Wireshark-dev] Is there a way to change the path (location) of wireshark PLUGINs?
>
> yenan wrote:
> > I found an option in configure file:
> >
> >
> > --with-plugins[=DIR] support plugins (installed in DIR, if supplied).
> > [default=yes, if possible]
> >
> > by using this option, is that means I can write a plugin in some
> > location , and includes the plugin?
>
> That option is not needed in order to have Wireshark support plugins; if
> your platform is capable of supporting plugins (all modern UN*Xes are;
> so is Windows, but you wouldn't use the configure script on Windows),
> Wireshark is built by default with plugin support. If you're building
> on UN*X, you could use "--without-pugins" to *remove* p lugin support.
>
> That option, if used with "=DIR", changes the "system" plugin directory,
> so that if you build Wireshark, the plugins will be installed there,
> rather than in the default directory, and the resulting Wireshark will
> look for plugins in that directory.
>
> > It requires a whole
> > direction(inculding makefile and souce codes) or only a lo file?
>
> What you need to install in the plugin directory is a .so file (on most
> UN*Xes, *including Mac OS X*) or a ".sl" file (I *think* that's the
> extension on 32-bit HP-UX) or a ".dll" file (on Windows).
>
> Currently, to build a plugin, you need to add a new subdirectory of the
> "plugins" directory of the Wireshark source and build Wireshark; we
> don't currently have support for conveniently building plugins by
> themselves.
>
> > can anyone please give me a simple example? Say I develop a plugin XX in
> > $home/plugin/xxx . , how can I include this plugin XXX to wireshark?
>
> By putting the plugin into $HOME/.wireshark/plugins, or the Windows
> equivalent, which is the "personal" plugin directory.
>
> The only directories in which Wireshark will look for plugins are the
> "system" plugin directory and the "personal" plugin directory.
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev



Windows Live Writer,支持离线撰写博客内容,随时随地想写就写。 立即使用!