development install issues

asked 2019-05-19 17:52:28 +0000

cmwDev
1 ●1 ●4 ●3

I'm trying to make a smaller custom version of Wireshark to log simple router traffic. I basically only need the time/date, incoming or outgoing, protocol (tcp, udp), remote IP address, remote name or message, remote port, local IP address, and local port. I won't be needing any of the "data" being sent or received and I am guessing that all I really need is the first packet of potential multiple packets. I suspect Wireshark will be able to do all of that, once I get into understanding it a lot more.

I have followed (hopefully correctly) the instructions in https://www.wireshark.org/docs/wsdg_h... and got down to 2.2.10 which deals with opening a visual studio command prompt. The doc file says I may have to hunt for it but... I explored the entire folder (program files x86, Microsoft visual studio, 2017).

I searched for both "native" and "command" in that folder and came up with nothing executable... As per the VS install instructions, I only selected the 'VC++ 2017 version... latest tools", Windows 10 SDK and Visual C++ tools for CMake.

Since apparently a lot of what happens is at the command line... and I really want to be able to get this right. Any hints on how to proceed would be deeply appreciate. Thanks kindly in advance :)

Gary

edit retag flag offensive close merge delete

add a comment

answered 2019-05-19 21:50:14 +0000

grahamb

flag of United Kingdom of Great Britain and Northern Ireland

23835 ●4 ●973 ●227 https://www.wireshark.org

The command line shortcuts should be installed in the Start Menu under the "Visual Studio 2017" entry with the folder icon. My installation has:

Developer Command Prompt for VS 2017
x64 Native Command Tools Prompt for VS 2017
x64_x86 Cross Tools Command Prompt for VS 2017
x86 Native Command Tools Prompt for VS 2017
x86_x64 Cross Tools Command Prompt for VS 2017

You can also DIY it, the old way, by opening a CMD prompt and running either:

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat"

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars32.bat"

for x64 and x86 respectively, assuming you've installed VS2017 in the default location.

edit flag offensive delete link

Comments

Interesting... my start menu only has the GUI program in the menu, there is no folder for it. But it does have those batch files in the location you stated. They are of course, not even close to the "names" given in the docs files link I listed above.

Anyway, thanks... :)

cmwDev ( 2019-05-20 05:58:27 +0000 )edit

The (missing) links are basically calls to run those batch files in a CMD prompt, nothing special.

The reason that you're missing the links is either MS have changed the VS installer to not add the links, or something in the VS install options has changed, or I have installed some optional component that you haven't.

grahamb ( 2019-05-20 08:42:59 +0000 )edit

So... I tried to follow the instructions for creating a build... I thought I had everything right except I didn't pay the proper attention to QT requirements since I already had it installed (5.12.0). Apparently I missed the MSVC 2017 64 bit module, and the QT maintenance program showed it to be in 5.12.2, so I added that part in.

I did the vcvars64 batch file, and I added my own 'vars' batch file to set the WireShark and QT base dir's. I changed to the Development folder (which contains the wireshark source from GIT), made the wsbuild32 folder, changed to that, and ran the cmake (cmake -G "Visual Studio 15 2017 Win64" ..\wireshark) as per the documentation. It did some stuff, went out and downloaded a pile of things into a folder it made (wireshark-win64-libs) and started doing other things.

Ended up with ...(more)

cmwDev ( 2019-05-23 19:20:58 +0000 )edit

The CMakeError.log isn't really relevant, as there will be a lot of failed tests there as CMake works out what is available and works on your platform.

The output from the CMake config log is much more relevant, and indicates that the LEX package isn't available in your system. This is provided by the winflexbison package and unfortunately the instructions to install this seem to have disappeared from the Developers Guide. If you installed the extra packages via Chocolatey, much the easiest way IMHO, then run cinst -y winflexbison.

grahamb ( 2019-05-23 21:28:44 +0000 )edit

Well... there has been *some progress. I found the doc section for winflexbison, it was something I definitely missed (2.2.9), my bad. And I took a closer look at Python as well. Some of the errors showing in the command window hinted that it wasn't there, but it was. The problem is, I installed it from the web link, and it defaulted to a folder called Python37-32. I didn't want to just rename the folder so I removed the program and used Choco to install it instead. It did put it in Python37. I nuked all of the libs and the contents of the wsbuild32 folder (ponders.. should I have called it wsbuild64 instead?) Anyway, doing the cmake and things went a lot further. Now there are multiple folders inside the wsbuild folder, unlike before there were only a few cmake things. The cmd window showed ...(more)

cmwDev ( 2019-05-24 17:21:42 +0000 )edit

see more comments

development install issues

1 Answer

Comments

Your Answer

Question Tools

Stats

development install issues edit

1 Answer

Comments

Your Answer

Question Tools

Stats

development install issues