ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Ethereal to Wireshark issues

From: "Steve Grinwis" <sgrinwis@xxxxxxx>
Date: Wed, 26 Jul 2006 09:53:22 -0400
The fact that you have to do an install-dep isn't documented anywhere...
It might not be a bad thing to add to readme.win32.  

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Peter
Johansson
Sent: Wednesday, July 26, 2006 6:19 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Ethereal to Wireshark issues

That is exactly why!

/ Peter

Jaap Keuter wrote:
> Hi,
>
> Isn't that why we have the install-deps build target?
>
> Thanx,
> Jaap
>
> On Wed, 26 Jul 2006, Graham Bloice wrote:
>
>   
>>> I rebuilt Wireshark to see if I could find any errors in the build.
I
>>> came across a few things.
>>>
>>>       
>> <SNIP>
>>
>>     
>>>         rm -rf 0.99.2
>>>
>>>
>>> It actually removes the 0.99.2 directory after it builds the
plug-ins.
>>> And the whole "Cannot find module" error looks very similar to the
error
>>> I get at run time.   Any thoughts?
>>>
>>>
>>>       
>> On windows, you can't run Wireshark from the build directory.  The
makefiles
>> temporarily create an environment that can run the exe to generate
some docs
>> etc., then destroy it.
>>
>> I have a batch file that I run after building that copies all the
dll's and
>> exe's to the appropriate places that a previous standard install has
created
>> and I then run the app from there.
>>
>> You can also install nsis and make an installer, but that takes a lot
longer
>> than just copying the executables.
>>
>> Graham



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.