> > > 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.
I think I've found an easier solution to run inside the source tree: Just the the PATH variable to all the libdirs. So far I have only tried this manually but I've finally managed to run capinfos (and get the usage output :-) If I find the time I'll add automatic PATH modification tomorrow evening, the idea is something like: check whether path has already been modified. if not: set( ENV{PATH} $ENV{PATH} ${CMAKE_BINARY_DIR}/lib <list> <of> <lib> <dirs> ) Feel free to beat me to it ;-) Good night Jörg -- Joerg Mayer <jma...@loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe