Using the install-deps build target fixed the problem. It works
like a charm (well... it loads the plugin). Now the only problems that
I have are ones with my code. And I can deal with my code. Thanks so
From: [email protected]
[mailto:[email protected]] On Behalf Of Jaap Keuter
Sent: Wednesday, July 26, 2006 5:11 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Ethereal to Wireshark issues
Isn't that why we have the install-deps build target?
On Wed, 26 Jul 2006, Graham Bloice wrote:
> > I rebuilt Wireshark to see if I could find any errors in the build.
> > came across a few things.
> > rm -rf 0.99.2
> > It actually removes the 0.99.2 directory after it builds the
> > And the whole "Cannot find module" error looks very similar to the
> > I get at run time. Any thoughts?
> On windows, you can't run Wireshark from the build directory. The
> temporarily create an environment that can run the exe to generate
> etc., then destroy it.
> I have a batch file that I run after building that copies all the
> exe's to the appropriate places that a previous standard install has
> and I then run the app from there.
> You can also install nsis and make an installer, but that takes a lot
> than just copying the executables.
> Wireshark-dev mailing list
> [email protected]
Wireshark-dev mailing list
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.