Guy Harris wrote: >I think at least once I've had my path set incorrectly when building Wireshark >on Windows, and getting the wrong command run - a Cygwin port of some UN*X >command being run instead of some other Windows tool that had the same name >but was a different tool. I think that's happened for me at least once with >"mt" - and, if not me, with somebody else asking wireshark-dev about it. > >That's why I wanted you to run "where mt.exe", to see whether it was picking >up Cygwin's "mt". From the output you got, it appears that it wasn't picking >up Cygwin's "mt", so that's apparently not the cause of the problem.
For what it's worth, I've definitely had path trouble building Wireshark on Windows (with Cygwin installed and in the path) and have found that the Cygwin-supplied "which" command is very helpful to sort this out. On my system, I use a batch file that explicitly sets the path (rather than the often recommended method of appending to the path) to avoid exactly this kind of problem. It looks like this: set PATH=...(long explicit path with Visual Studio stuff first) set WIRESHARK_TARGET_PLATFORM=win32 call "c:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" title Command Prompt (VC++ 2008) Ed ___________________________________________________________________________ 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
