On 11/2/20 8:51 AM, Maynard, Chris via Wireshark-dev wrote:
>> From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf Of Graham Bloice
>> Sent: Monday, November 2, 2020 11:04 AM
>> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
>> Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows
>>
>> FWIW, Strawberry Perl has failed to update for me with chocolatey the last few versions, my workaround is to uninstall and then install again.
>
> Yeah, that was my next plan when I get a chance.
>
>> There is a winflexbison3 package that has newer versions, and both nsis and wixtoolset are available as chocolatey packages.
>>
>> I don't think apache-fop or xsltproc are required now (I don't have them in my current VM's) and I've never installed speex.
>>
>
> I've had my laptop for awhile so it may very well have some packages installed that are no longer needed. That said, if xsltproc isn't required, then it should probably no longer be mentioned in the Developer Guide as a requirement: https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html#ChSetupAsciidoctor. If there's a chocolatey nsis package available, then it might be worth mentioning that in the Developer Guide though: https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html#_optional_create_a_wireshark_installer.
We use xsltproc to generate the HTML and HTML Help versions of the user and developer guides: https://www.wireshark.org/docs/wsdg_html_chunked/ChToolsDocumentationToolchain.html. The Windows builders build those targets but it's not required if you just want a Wireshark executable.
We used to use Apache FOP to build the PDF documentation but asciidoctor-pdf supports that directly.
