OSQA is unmaintained. Help us figure out where to go from here.

i am tring to build 2.4 version of wireshark. but getting the folowing error:

"D:\wireshark-2.4\wsbuild\Wireshark.sln" (default target) (1) ->
"D:\wireshark-2.4\wsbuild\doc\docs.vcxproj.metaproj" (default target) (21) ->
"D:\wireshark-2.4\wsbuild\doc\docs.vcxproj" (default target) (92) ->
(CustomBuild target) ->
  C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006: "cmd.exe" exited with code 2. [D:\wireshark-2.4\wsbuild\doc\docs.vcxproj]
"D:\wireshark-2.4\wsbuild\Wireshark.sln" (default target) (1) ->
"D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj.metaproj" (default target) (75) ->
"D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj" (default target) (104) ->
(ClCompile target) ->
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(888): error C2275: 'ProtoField' : illegal use of this type as an expression [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(888): error C2146: syntax error : missing ';' before identifier 'f' [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(888): error C2065: 'f' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(889): error C2065: 'f' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(890): error C2065: 'f' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(890): error C2223: left of '->hfid' must point to struct/union [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\wslua\wslua_tree.c(890): error C2198: 'proto_field_is_referenced' : too few arguments for call [D:\wireshark-2.4\wsbuild\epan\wslua\wslua.vcxproj]
"D:\wireshark-2.4\wsbuild\Wireshark.sln" (default target) (1) ->
"D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj.metaproj" (default target) (19) ->
"D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj" (default target) (89) ->
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(434): error C2275: 'guint32' : illegal use of this type as an expression [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(434): error C2146: syntax error : missing ';' before identifier 'response_code' [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(434): error C2065: 'response_code' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(436): error C2065: 'response_code' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(438): error C2065: 'response_code' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(439): error C2065: 'response_code' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-usb-i1d3.c(442): error C2065: 'response_code' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-ipv6.c(2098): error C2275: 'guint16' : illegal use of this type as an expression [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-ipv6.c(2098): error C2146: syntax error : missing ';' before identifier 'mapped_port' [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-ipv6.c(2098): error C2065: 'mapped_port' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]
  D:\wireshark-2.4\wireshark-2.4.0\epan\dissectors\packet-ipv6.c(2109): error C2065: 'mapped_port' : undeclared identifier [D:\wireshark-2.4\wsbuild\epan\dissectors\dissectors.vcxproj]

i used the same configuarations for 2.2 version it was building correctly without errors.

asked 02 Aug, 01:57

lucky15's gravatar image

lucky15
6458
accept rate: 0%

edited 02 Aug, 03:13

grahamb's gravatar image

grahamb ♦
19.5k330205

Looks like a header issue. What compiler are you using? Have you tried deleting CMakeCache.txt (or the entire build directory) and rerunning the CMake generation step?

(02 Aug, 03:14) grahamb ♦

this is fresh copy build.It doesnt have any previous cmake cache.txt .I downloaded from website and built it. used:

set PATH=D:\cmake\cmake-3.7.1-win64-x64\bin;%PATH%
call "c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" x86_amd64
set WIRESHARK_TARGET_PLATFORM=win64
set QT5_BASE_DIR=C:\Qt\Qt5.6.2\5.6\msvc2013_64
set WIRESHARK_BASE_DIR=D:\wireshark-2.4\wireshark-2.4.0

followed the steps from step of 2.2.10: https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html running from visual studio cmd prompt of VS2013 x64 Native Tools Command Prompt for a 64-bit version.

(02 Aug, 03:33) lucky15

The WSDG doesn't ask you to run vcvarsall.bat.

Can you open a new VS Command prompt and complete the same steps but omitting the call to vcvarsall.bat?

(02 Aug, 05:20) grahamb ♦

thanks for replying. but facing the same problem the above errors are coming after removing the call for VS. i used the same configuartion to build 2.2 version and i didnt face any issue.please help me to resolve for 2.4 version.

(02 Aug, 21:53) lucky15

Are you building from a git clone, or a source tarball?

(03 Aug, 00:01) grahamb ♦

from source tar file from webisite:https://www.wireshark.org/download.html

(03 Aug, 01:17) lucky15

wrote a bat file

@echo off
echo Adding things to the path…
set PATH=%PATH%;.
set CYGWIN=nodosfilewarning
set WIRESHARK_TARGET_PLATFORM=win64
set WIRESHARK_CYGWIN_INSTALL_PATH=D:\softwares\cygwin
set PATH=D:\softwares\cmake\cmake-3.7.1-win64-x64\bin;%PATH%
set PATH=D:\softwares\python;%PATH%
set VisualStudioVersion=12.0
echo Setting up Visual Studio environment…
call "c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" x86_amd64
set WIRESHARK_TARGET_PLATFORM=win64
set QT5_BASE_DIR=C:\Qt\Qt5.6.2\5.6\msvc2013_64
set WIRESHARK_BASE_DIR=D:\wireshark-2.4\wireshark-2.4.0
(03 Aug, 01:46) lucky15

Presumably this is run from a regular cmd prompt due to the call to vcvarsall.bat. If you're using a VS command prompt then do NOT make that call.

Note that if you're running on an x64 OS and building an x64 version of Wireshark, then using the native x64 compilers is recommended, i.e. ...\vcvarsall.bat x64

The line set PATH=%PATH%;. is probably redundant.

The line set VisualStudioVersion=12.0 is not required for VS2013.

Using the above batch file in a regular command prompt, omitting the path adjustments for cmake and python as they're already on my path, and amending the other env vars to suit my build env, the cmake generation and build worked for me using VS2013 and a git clone of the repo.

I suspect either something wrong with your environment variables, can you post the output of "set" after you have run your batch file?

(03 Aug, 03:21) grahamb ♦

-- Configuring done -- Generating done -- Build files have been written to: D:/wireshark-2.4/msbuild

D:\wireshark-2.4\msbuild>echo %PATH%
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\;C:\Program Files (x86)\MSBuild\12.0\bin;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 12.0\
VC\BIN\x86_amd64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools;C:\windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\M
icrosoft Visual Studio 12.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;D:\softwares\python;D:\softwares\cmake\cmake-3.7.1-win64-x64\bin;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonE
xtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\12.0\bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64;C:\windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE;
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x6

D:\wireshark-2.4\msbuild>echo %WIRESHARK_CYGWIN_INSTALL_PATH%
D:\softwares\cygwin

D:\wireshark-2.4\msbuild>echo %QT5_BASE_DIR%
C:\Qt\Qt5.6.2\5.6\msvc2013_64

D:\wireshark-2.4\msbuild>echo %WIRESHARK_BASE_DIR%
D:\wireshark-2.4\wireshark-2.4.0

when i try to copy my full cmake command output i am not able to paste it here in comments.how can i do that?or how can i upload my cmake output file ?

(03 Aug, 03:56) lucky15

Reformatting your path, and then sorting gives this:

C:\Program Files (x86)\HTML Help Workshop
C:\Program Files (x86)\HTML Help Workshop
C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\x86_amd64
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages
C:\Program Files (x86)\MSBuild\12.0\bin
C:\Program Files (x86)\MSBuild\12.0\bin\amd64
C:\Program Files (x86)\Windows Kits\8.1\bin\x6
C:\Program Files (x86)\Windows Kits\8.1\bin\x86
C:\windows\Microsoft.NET\Framework\v4.0.30319
C:\windows\Microsoft.NET\Framework64\v4.0.30319
D:\softwares\cmake\cmake-3.7.1-win64-x64\bin
D:\softwares\python

And you can see that you have both x86 and x64 Visual Studio and Windows Kits elements on your path, along with other duplicate entries.

Can you confirm what command prompt you are using, is it a regular one or a Visual Studio Tools command prompt?

Either way can you show you PATH straight after opening the prompt and BEFORE you have done anything else.

(03 Aug, 05:41) grahamb ♦

using visual studio command prompt.

C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64>d:

D:\>echo %PATH%
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\12.0\bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64;C:\windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x64;
(03 Aug, 05:57) lucky15

And the separated version is:

C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow
C:\Program Files (x86)\MSBuild\12.0\bin\amd64
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64
C:\windows\Microsoft.NET\Framework64\v4.0.30319
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools
C:\Program Files (x86)\HTML Help Workshop
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools
C:\Program Files (x86)\Windows Kits\8.1\bin\x64

Which looks about right for an x64 build, however you seem to be missing all the other standard path elements e.g.

C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem

Did you omit some of the path?

Anyway, you can now run your batch file, but as I've mentioned several times before DO NOT include the line to call vcvarsall.bat, it's not needed for a VS command prompt.

(03 Aug, 06:10) grahamb ♦

i have removed the vcvarsall.bat from the batch file.still observed the same.

D:\wireshark-2.4\msbuild>echo %PATH%
D:\softwares\python;D:\softwares\cmake\cmake-3.7.1-win64-x64\bin;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\12.0\bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64;C:\windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x64;C:\Program Files (x86)\Windows Kits\8.1\bin\x86
(03 Aug, 22:34) lucky15

That PATH, as far as compilation goes is fine, however it's missing vital normal elements that belong on the path as I mentioned previously.

As for both the x64 and x86 windows kits being on the path, I hadn't noticed before, but a VS x64 command prompt does add them both.

Did you try building from that prompt?

(04 Aug, 02:08) grahamb ♦

ya i removed them.i tried again same problem.i am quite suprised how the 2.2 version got built without any problem with the same configuartions ,in that configuartion batch file i used "call for vcvarsall" also.

(04 Aug, 02:20) lucky15

I don't know what to try next, your PATH seems hopelessly broken.

Maybe try removing the line set PATH=%PATH%;. from your batch file. I think that is intended to add the current directory to the path but it might be deleting the existing path.

Use this batch file in a Visual Studio Command Prompt:

@echo off
echo Adding things to the path...
set PATH=%PATH%;D:\softwares\cmake\cmake-3.7.1-win64-x64\bin
set PATH=%PATH%;D:\softwares\python
echo Setting env vars...
set CYGWIN=nodosfilewarning
set WIRESHARK_CYGWIN_INSTALL_PATH=D:\softwares\cygwin
set WIRESHARK_TARGET_PLATFORM=win64
set QT5_BASE_DIR=C:\Qt\Qt5.6.2\5.6\msvc2013_64
set WIRESHARK_BASE_DIR=D:\wireshark-2.4\wireshark-2.4.0
(04 Aug, 03:06) grahamb ♦

thanks for suggestions.but no luck..

(04 Aug, 04:12) lucky15

tried with cmake-3.9 set up .got the errors with first cmake command only.i gave the ENV variables mentioned as above @grahamb suggested.part of it attached:

-- Generating build using CMake 3.9.0 CMake Deprecation Warning at CMakeLists.txt:51 (cmake_policy): The OLD behavior for policy CMP0011 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. CMake Deprecation Warning at CMakeLists.txt:60 (cmake_policy): The OLD behavior for policy CMP0026 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD.

-- Building for win64 using Visual Studio 12 2013 Win64 Working in D:\wireshark-2.4\wireshark-2.4.0\wireshark-win64-libs-2.4 Tag 2017-05-11 found. Skipping.

-- Found PythonInterp: D:/softwares/python/python.exe (found version "3.5.2") -- Checking for c-compiler flag: /MP -- Checking for c-compiler flag: /Zo -- Checking for c-compiler flag: /w34295 /w34189 /wd4200 -- Checking for c++-compiler flag: /MP -- Checking for c++-compiler flag: /Zo -- Checking for c++-compiler flag: /w34295 /w34189 /wd4200 statuscheck linker flag - test linker flags: -Wl,--as-needed statuscheck linker flag - test linker flags: -pie

-- -- PCAP FOUND -- PCAP includes: D:/wireshark-2.4/wireshark-2.4.0/wireshark-win64-libs-2.4/WpdPack/Include -- PCAP libs: D:/wireshark-2.4/wireshark-2.4.0/wireshark-win64-libs-2.4/WpdPack/Lib/x64/wpcap.lib -- POD FOUND -- PERL FOUND -- Perl executable: D:/softwares/cygwin/bin/perl.exe -- Found PythonInterp: D:/softwares/python/python.exe (found suitable version "3.5.2", minimum required is "2") -- PYTHONINTERP FOUND

-- Could NOT find SETCAP (missing: SETCAP_EXECUTABLE) -- SETCAP NOT FOUND -- Could NOT find SH (missing: SH_EXECUTABLE) CMake Error at cmake/modules/FindSH.cmake:29 (message): The bash executable (SH_EXECUTABLE-NOTFOUND) isn't from Cygwin. Check your path Call Stack (most recent call first): CMakeLists.txt:942 (find_package)

-- Configuring incomplete, errors occurred!

(04 Aug, 06:19) lucky15

CMake Error at cmake/modules/FindSH.cmake:29 (message): The bash executable (SH_EXECUTABLE-NOTFOUND) isn't from Cygwin. Check your path

What does where bash show in the command prompt?

(04 Aug, 06:24) grahamb ♦

Have you installed WSL? When I installed it just to play with it a bit, I found that it broke Wireshark compilation because it was picking up bash.exe in C:\Windows\System32\ (I believe that's where it was located) instead of Cygwin's bash.exe.

It would be nice if Wireshark could be compiled on a system with WSL installed, but I didn't really have a need for it, so I just ended up disabling WSL. (Well, it probably can be compiled on a system with WSL installed, but probably not without some changes.)

If you do have WSL installed and either need it or would rather not uninstall it, then it might make sense to create a Windows VM (without WSL installed) specifically for compiling Wireshark. I know @graham has advocated this for a long time and it would almost certainly resolve issues like this.

(04 Aug, 06:57) cmaynard ♦♦

The git "Unix tools" is another source of an errant bash.

However as the OP is showing a path that seems to be abridged, i.e. no System32, it's very difficult to say what's being found. I might modify the CMake check to print the path to the non-Cygwin bash.

(06 Aug, 13:13) grahamb ♦

i am not able to get the path for cmake/modules/FindSH.cmake.

(06 Aug, 23:46) lucky15

Actually CMake already prints out the path to the bash executable it found, you should see that in the CMake output.

However, I misread the output you show, as it seems that CMake didn't find bash as the path is SH_EXECUTABLE_NOTFOUND, and FindSH, somewhat unhelpfully, insists that this isn't a Cygwin bash.

Do you have D:\softwares\Cygwin\bin\bash.exe, if not install it via Cygwin setup? While CMake will complete without bash, when building generation of the docs will fail.

(07 Aug, 03:48) grahamb ♦

yes,its present in the path and even the for PERL also its not showing cgwin path.when i tried to copy my cmake output in comments i am not able to paste it. but for same configuartions of 3.7.1 atleast cmake errors were not coming. should i upgrade any other sofware. MY compiler is:

The C compiler identification is MSVC 18.0.21005.1 The CXX compiler identification is MSVC 18.0.21005.1

(07 Aug, 04:16) lucky15

Changing the compiler won't fix issues with CMake.

As mentioned by @cmaynard above, I highly recommend (and use this myself) creating VM's for Wireshark work on Windows, and only installing the required items in the VM. This prevents path complications among other things.

If you don't have enough space in a comment to post complete output, either use a file sharing service such as Google Drive, DropBox etc. or post the text in an "answer" which can then be converted to a comment.

(07 Aug, 04:30) grahamb ♦
showing 5 of 25 show 20 more comments
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×41

question asked: 02 Aug, 01:57

question was seen: 316 times

last updated: 07 Aug, 04:30

p​o​w​e​r​e​d by O​S​Q​A