Wireshark-dev: Re: [Wireshark-dev] Build Failure.Please help!!

From: "Kumar, Hemant" <kumarh@xxxxxxxxxxxx>
Date: Tue, 10 Jun 2008 18:18:21 -0700
Hi

Do you mean on win32 platform, in the main directory wireshark-1.0.0, the wireshark executable which is created will not work as all the required dlls are not copies to this directory and as a result on launching it complains saying that "some dll files not found"?

Its works fine from gtk directories though as of course during in the end build process all dll and required dependencies are xcopied to these gtk directories.

Thanks
Hemant

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Bill Meier
Sent: Tuesday, June 10, 2008 4:44 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Build Failure.Please help!!

Tobias Wärre wrote:
> Hi
> I'm not fully immersed of the details of the build process, but I think (well know, but I'm a
 > bit modest... ;) ) it has to do with dependencies.
> The C:\wireshark-1.0.0\ folder and all subfolders except
> for those created during a
> build (to see the effect do a 'nmake -f Makefile.nmake distclean'
> and then a 'nmake -f Makefile.nmake all'
> and watch what folders that are created). In the end of the build, all necessary files are
> copied (using xcopy in windows) into /wireshark-gtk-1 and /wireshark-gtk2 and
> in those folders all dependencies are on the right places.

> The C:\wireshark-1.0.0\ is only a placeholder of the development files until the build is ready.
>
> Was I fussy or (or perhaps even wrong) somewhere? If so, please say that.
>

You are quite correct: the wireshark-gt? directories are especially
created and populated to contain all the dependencies (dlls and etc)
required to run wireshark, tshark & etc on Windows in the development
environment.


_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev