Wireshark mailing list archives

Re: Building on Windows with CMake: Status and help needed


From: Graham Bloice <graham.bloice () trihedral com>
Date: Mon, 7 Oct 2013 15:42:21 +0100

On 7 October 2013 15:37, Gerald Combs <gerald () wireshark org> wrote:

On 10/6/13 4:35 PM, Bill Meier wrote:
On 10/6/2013 7:27 PM, Joerg Mayer wrote:
The executables now compile and link except the gtk and qt guis.
I have not yet been able to run the executables as running the binaries
inside the build tree doesn't seem to work (unlike on linux).
Ideas how to get this to work?

Thanks
    Jörg


This is undoubtedly about the fact that Makefile.nmake copies lots of
DLLs and etc to a separate "run" directory.

The exe's won't run from the build dir on Windows.

See install_all: target in Makefile.nmake (top-level)

...
# "install-all" will copy all files needed to run Wireshark/Tshark
# to the INSTALL_DIR, so you can run/debug Wireshark/Tshark from there.
install-all: install-generated-files
...

Dependency Walker (www.dependencywalker.com) is pretty useful for
finding dependent DLLs.


I forgot to mention that when I mentioned "dumpbin /dependants" earlier.
___________________________________________________________________________
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: