This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Html Help in Wireshark 2.0 build

0

I setup the Windows build environment for Wireshark 2.0 and I'm trying to build. I should have all the versions of things from the Win32/Win64 Step-by-Step guide. I downloaded the source tarball from website and have made no modifications to anything not in the guide.

I make it through the cmake process, but it seems to absolutely refuse to find Html Help Workshop. It is installed along with about every docbook module in cygwin.

I think this is the issue I'm having because the docbook projects fail to build.

This is the end of the cmake step (didn't include found optional packages, this question is long enough):

-- The following REQUIRED packages have been found:

  • PowerShell
  • GLIB2
  • GTHREAD2
  • LEX
  • YACC

-- The following OPTIONAL packages have not been found:

  • CAP
  • Gettext
  • M
  • PkgConfig
  • SBC , SBC Codec for Bluetooth A2DP stream playing , <www: <a="" href="http://git.kernel.o">http://git.kernel.o rg/cgit/bluetooth/sbc.git>
  • SETCAP
  • YAPP
  • HTMLHelp

-- Configuring done -- Generating done -- Build files have been written to: C:/Development/WiresharkBuild32

This is the mess I get when I run msbuild: Build FAILED.

   "C:\Development\WiresharkBuild32\Wireshark.sln" (default target) (1) ->
   "C:\Development\WiresharkBuild32\docbook\release_notes_html.vcxproj.meta
   proj" (default target) (59) ->
   "C:\Development\WiresharkBuild32\docbook\release_notes_html.vcxproj" (de
   fault target) (70) ->
   (CustomBuild target) ->
     C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCo
   mmon.targets(170,5): error MSB6006: "cmd.exe" exited with code 2. [C:\De
   velopment\WiresharkBuild32\docbook\release_notes_html.vcxproj]

"C:\Development\WiresharkBuild32\Wireshark.sln" (default target) (1) -> "C:\Development\WiresharkBuild32\docbook\user_guide_docbook.vcxproj.meta proj" (default target) (64) -> "C:\Development\WiresharkBuild32\docbook\user_guide_docbook.vcxproj" (de fault target) (68) -> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCo mmon.targets(170,5): error MSB6006: "cmd.exe" exited with code 2. [C:\De velopment\WiresharkBuild32\docbook\user_guide_docbook.vcxproj]

"C:\Development\WiresharkBuild32\Wireshark.sln" (default target) (1) -> "C:\Development\WiresharkBuild32\docbook\developer_guide_docbook.vcxproj .metaproj" (default target) (54) -> "C:\Development\WiresharkBuild32\docbook\developer_guide_docbook.vcxproj " (default target) (69) -> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCo mmon.targets(170,5): error MSB6006: "cmd.exe" exited with code 2. [C:\De velopment\WiresharkBuild32\docbook\developer_guide_docbook.vcxproj]

0 Warning(s) 3 Error(s)

Thanks, Brian

asked 16 Dec ‘15, 20:11

brwiese's gravatar image

brwiese
26111211
accept rate: 50%


2 Answers:

0

There seems to be a couple of issues here:

  1. CMake fails to report it finds the HTML Help package, even when it does find the help compiler.
  2. Your build fails for as yet unknown reasons.

For (1), this requires an upstream fix by CMake, or a local override of the upstream FindHTMLHelp.cmake to report the package as found.

For (2), can you look at the CMakeCache.txt file in your build directory for lines with HTML_HELP_ in them? These will be the path to the compiler, the path to the includes for the compiler and the path the the library.

To minimise the output when testing you can just build a single docbook project, e.g.

msbuild /m /p:Configuration=RelWithDebInfo .\docbook\release_notes_html.vcxproj

To turn on more logging, and log to a file append the following to the msbuild command:

/fl /flp:logfile=path\to\log\file;verbosity=diagnostic

You might need to quote some of these parameters depending on the command shell you use. When debugging builds, it's helpful to remove the /m flag to stop parallel building, so nodes are built serially and the output is less difficult to follow.

answered 17 Dec '15, 03:31

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

edited 17 Dec '15, 03:35

0

So, if I get the source using git this problem goes away. The tar balls for windows are either old, not complete, or just wrong.

Thanks, Brian

answered 22 Jan '16, 13:09

brwiese's gravatar image

brwiese
26111211
accept rate: 50%