Wireshark-dev: Re: [Wireshark-dev] Doxygen causing build error
From: "Maynard, Chris" <Christopher.Maynard@xxxxxxx>
Date: Mon, 23 Apr 2018 18:13:56 +0000
> Are the wsar_html or wsar_html_zip targets being built by default, i.e. without
> them being specified? Neither of them uses the "ALL" flag so that shouldn't
> happen.
 
As far as I can tell, it *appears* to be the case that those targets are attempting to be built; however, with Cygwin’s doxygen, it fails as follows:
 
-- DOXYGEN FOUND
-- DOXYGEN executable: C:/cygwin64/bin/doxygen.exe
 
Project "D:\wireshark\builds\win64\master\Wireshark.sln" (1) is building "D:\wi
reshark\builds\win64\master\wsar_html.vcxproj.metaproj" (135) on node 1 (defaul
t targets).
Project "D:\wireshark\builds\win64\master\wsar_html.vcxproj.metaproj" (135) is
building "D:\wireshark\builds\win64\master\wsar_html.vcxproj" (136) on node 1 (
default targets).
InitializeBuildStatus:
  Touching "x64\RelWithDebInfo\wsar_html\wsar_html.tlog\unsuccessfulbuild".
CustomBuild:
  Building Custom Rule D:/wireshark/src/master/CMakeLists.txt
  CMake does not need to re-run because D:\wireshark\builds\win64\master\CMakeF
  iles\generate.stamp is up-to-date.
CUSTOMBUILD : warning : tag INPUT: input source `D:/wireshark/src/master/cmbuil
d' does not exist [D:\wireshark\builds\win64\master\wsar_html.vcxproj]
CUSTOMBUILD : error : Failed to open temporary file /cygdrive/d/wireshark/build
s/win64/master/D:/wireshark/builds/win64/master/doxygen_objdb_20212.tmp [D:\wir
eshark\builds\win64\master\wsar_html.vcxproj]
  Exiting...
Done Building Project "D:\wireshark\builds\win64\master\wsar_html.vcxproj" (def
ault targets) -- FAILED.
 
Done Building Project "D:\wireshark\builds\win64\master\wsar_html.vcxproj.metap
roj" (default targets) -- FAILED.
 
Done Building Project "D:\wireshark\builds\win64\master\Wireshark.sln" (default
targets) -- FAILED.
 
 
Build FAILED.
 
"D:\wireshark\builds\win64\master\Wireshark.sln" (default target) (1) ->
"D:\wireshark\builds\win64\master\ALL_BUILD.vcxproj.metaproj" (default target)
(2) ->
"D:\wireshark\builds\win64\master\copy_qt_dlls.vcxproj.metaproj" (default targe
t) (34) ->
"D:\wireshark\builds\win64\master\wireshark.vcxproj.metaproj" (default target)
(35) ->
"D:\wireshark\builds\win64\master\ui\qt\qtui.vcxproj.metaproj" (default target)
(58) ->
"D:\wireshark\builds\win64\master\ui\qt\qtui.vcxproj" (default target) (65) ->
(ClCompile target) ->
  cl : Command line warning D9002: ignoring unknown option '/Qspectre' [D:\wire
shark\builds\win64\master\ui\qt\qtui.vcxproj]
 
 
"D:\wireshark\builds\win64\master\Wireshark.sln" (default target) (1) ->
"D:\wireshark\builds\win64\master\wsar_html.vcxproj.metaproj" (default target)
(135) ->
"D:\wireshark\builds\win64\master\wsar_html.vcxproj" (default target) (136) ->
(CustomBuild target) ->
  CUSTOMBUILD : warning : tag INPUT: input source `D:/wireshark/src/master/cmbu
ild' does not exist [D:\wireshark\builds\win64\master\wsar_html.vcxproj]
 
 
"D:\wireshark\builds\win64\master\Wireshark.sln" (default target) (1) ->
"D:\wireshark\builds\win64\master\wsar_html.vcxproj.metaproj" (default target)
(135) ->
"D:\wireshark\builds\win64\master\wsar_html.vcxproj" (default target) (136) ->
(CustomBuild target) ->
  CUSTOMBUILD : error : Failed to open temporary file /cygdrive/d/wireshark/bui
lds/win64/master/D:/wireshark/builds/win64/master/doxygen_objdb_20212.tmp [D:\w
ireshark\builds\win64\master\wsar_html.vcxproj]
 
    2 Warning(s)
    1 Error(s)
 
And with native doxygen, there’s just the 2 warnings, presumably because my build environment is different than the buildbot environment:
 
-- DOXYGEN FOUND
-- DOXYGEN executable: C:/Program Files/doxygen/bin/doxygen.exe
 
"D:\wireshark\builds\win64\master\Wireshark.sln" (default target) (1) ->
"D:\wireshark\builds\win64\master\wsar_html.vcxproj.metaproj" (default target)
(135) ->
"D:\wireshark\builds\win64\master\wsar_html.vcxproj" (default target) (136) ->
(CustomBuild target) ->
  CUSTOMBUILD : warning : tag INPUT: input source `D:/wireshark/src/master/cmbu
ild' does not exist [D:\wireshark\builds\win64\master\wsar_html.vcxproj]
  CUSTOMBUILD : warning : source D:/wireshark/src/master/cmbuild is not a reada
ble file or directory... skipping. [D:\wireshark\builds\win64\master\wsar_html.
vcxproj]
 
With the native doxygen, the wsar_html directory is created in the build directory and there is doxygen output there, but cygwin’s doxygen fails well before anything is generated.
- Chris
 
> -----Original Message-----
> Behalf Of Gerald Combs
> Sent: Monday, April 23, 2018 12:52 PM
> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
> Subject: Re: [Wireshark-dev] Doxygen causing build error
>
> Are the wsar_html or wsar_html_zip targets being built by default, i.e. without
> them being specified? Neither of them uses the "ALL" flag so that shouldn't
> happen.
>
> I'm not sure if it's worth the effort to try to make doxygen.cfg compatible with
> Cygwin. I'll upload a change that tries to avoid building with it.
>
>
> On 4/21/18 11:57 PM, Roland Knall wrote:
> > Cygwins oxygen had issues for me in the past as well. Installing a
> > native version seems to work without any hiccups though.
> >
> > regards
> > Roland
> >
> > On Sun, Apr 22, 2018 at 12:58 AM, Maynard, Chris
> wrote:
> >
> >     Has anyone successfully compiled Wireshark on Windows with Doxygen
> >     installed?  I have Cygwin’s doxygen installed, but Wireshark fails to
> >     build after this commit:
> >
> c866713b2f75e9b11a30468b81be7d3d5e
> >
> > <https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=a
> > d84eec866713b2f75e9b11a30468b81be7d3d5e>.____
> >
> >     __ __
> >
> >     I noticed that neither of the Windows Server 2016 buildbots (x64 and
> >     x86) has Doxygen installed, so I temporarily just renamed it so cmake
> >     wouldn’t find it and now Wireshark successfully builds again.____
> >
> >     __ __
> >
> >     Maybe at least one of the Windows buildbots should have Doxygen
> >     installed?
 
 
 

CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information.  This message is intended solely for the use of the addressee.  If you are not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited.