Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Doxygen causing build error

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 23 Apr 2018 09:52:07 -0700
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
> <Christopher.Maynard@xxxxxxx <mailto:Christopher.Maynard@xxxxxxx>> 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:
>     https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=ad84eec866713b2f75e9b11a30468b81be7d3d5e
>     <https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=ad84eec866713b2f75e9b11a30468b81be7d3d5e>.____
> 
>     __ __
> 
>     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?____
> 
>     - Chris____
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     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.
> 
> 
>     ___________________________________________________________________________
>     Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
>     <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>     Archives:    https://www.wireshark.org/lists/wireshark-dev
>     <https://www.wireshark.org/lists/wireshark-dev>
>     Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>     <https://www.wireshark.org/mailman/options/wireshark-dev>
>                  mailto:wireshark-dev-request@xxxxxxxxxxxxx
>     <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
> 
> 
> 
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>