Wireshark mailing list archives

Re: building wireshark in linux


From: ajay seshadri <sesh_ajay () yahoo com>
Date: Thu, 29 Jul 2010 04:27:46 -0700 (PDT)

Thanks a lot Chris.


Since I am building it as a plugin, I actually paste the dll in the 
..wireshark\wireshark-gtk2\plugins\my_protocol folder to make it work. It 
doesn't show the added protocol otherwise.

I get this message : sudo: ./autogen.sh: command not found for ./autogen.sh. 
I have installed autoconf2.66, automake-1.9 and libtool-2.2. Am I missing out on 
the installation of any files?




________________________________
From: "Maynard, Chris" <Christopher.Maynard () GTECH COM>
To: Developer support list for Wireshark <wireshark-dev () wireshark org>
Sent: Tue, July 27, 2010 6:59:55 PM
Subject: Re: [Wireshark-dev] building wireshark in linux

 
1. export WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1
2. “./configure --prefix=${HOME}/build/root”: That’s an example of what you type 
on the command-line during the configure step.
 
As far as I know, everything in the README.pluginsis accurate and applicable.
 
BTW, on Windows, you don’t have to copy any plugin .dll’s anywhere.  Just run 
wireshark.exefrom the wireshark-gtk2\directory.
- Chris
 
 
From:wireshark-dev-bounces () wireshark org 
[mailto:wireshark-dev-bounces () wireshark org] On Behalf Of ajay seshadri
Sent: Tuesday, July 27, 2010 3:03 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] building wireshark in linux
 
Hi Chris,

Thanks a lot for the reply. I went through the description for unix files in 
doc/README.plugins. 


They ask us to:
 
1. set an environment variable : WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 (can you 
please tell me where this change has to be made?)

2. set up a working root using - ./configure --prefix=${HOME}/build/root 
(again not sure where this change has to be made)
and build wireshark to install there using 'make install'

Can you please tell me if the steps for making changes to the existing Wireshark 
files and adding the make files to the dissector plugin directory remain the 
same?

Also, if I am not mistaken, setting up the working root will automatically  read 
the appropriate plugins from their respective paths, we don't have to copy paste 
the *.so files anywhere like we do it for *.dll in windows?

I could build it successfully in windows. I am relatively new to linux and hence 
had some doubts regarding the same. 


I would appreciate any help in this regard.

Thanks and Best Regards,
Ajay

________________________________
 
From:"Maynard, Chris" <Christopher.Maynard () GTECH COM>
To: Developer support list for Wireshark <wireshark-dev () wireshark org>
Sent: Tue, July 27, 2010 2:02:10 AM
Subject: Re: [Wireshark-dev] building wireshark in linux
Have you read doc/README.plugins?
- Chris
 
From:wireshark-dev-bounces () wireshark org 
[mailto:wireshark-dev-bounces () wireshark org] On Behalf Of ajay seshadri
Sent: Monday, July 26, 2010 3:14 PM
To: Developer support list for Wireshark
Subject: [Wireshark-dev] building wireshark in linux
 
Hi, 
 
What are the changes to be made to compile and run a Wireshark dissector plugin 
in Linux? The developer's manual gives in depth information about the changes to 
be made to the various files (including *.nmake) to compile it in windows. 
 
Is 'make all' sufficient in linux? Would it generate a *.so file? I would 
appreciate it if anyone could guide me in this regard. 
 
Thanks,
Ajay
 
 
CONFIDENTIALITY NOTICE: The contents of this email are confidential
 and for the exclusive use of the intended recipient. If you receive this
 email in error, please delete it from your system immediately and 
 notify us either by email, telephone or fax. You should not copy,
 forward, or otherwise disclose the content of the email.
 
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.



      
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: