Wireshark-users: [Wireshark-users] Re: FOLLOW UP - Re: cmake build error in migration from 4.4 to

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 5 Mar 2026 12:47:15 -0800
Hi John,

Downloading archive files into $GIT_WORK_TREE/_download is expected behavior in 4.6 and later. Prior to 4.6, we downloaded and extracted third party libraries using tools/win-setup.ps1 on Windows, and in 4.6 and later we download and extract third party libraries on Windows and macOS using cmake/modules/FetchArtifacts.cmake. As part of the change I moved the downloaded archives to _downloads in order to keep the archives and their extracted contents separate and to make it easier to clear the library directory when its contents are updated.

I'm not sure why FetchArtifacts is failing. I opened https://gitlab.com/wireshark/wireshark/-/merge_requests/23778 to make the failures more noisy; if you could update your copy of FetchArtifacts.cmake to match that might shed light on the issue.

On 3/5/26 12:34 PM, John Dill via Wireshark-users wrote:
Hi, thanks for the suggestion.

>4.4 still using win-setup.ps1

I tried copying that text into my 4.6.4 source tree for FetchArtifacts.cmake and still have the same behavior (hangs for about a minute then times out).

I do see a "wireshark-x64-libs-4.6" folder getting created under WIRESHARK_BASE_DIR.

And after running the cmake -G command, the <wireshark_src_dir> has a "_download" subfolder with a 0 KB size bcg729-1.0.4-win64ws.zip

Any thoughts?

Has anyone heard of other Windows 11 users having this wireshark 4.6 build problem?

Thanks,
John D.




ATTENTION: The information contained in this message is intended for the addressee only and may contain Confidential / Controlled Unclassified Information (CUI). If you are not the intended addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the individual(s) and not necessarily of the organization. No guarantee is implied that this message or any attachment is virus free or has not been intercepted and amended.

_______________________________________________
Wireshark-users mailing list -- wireshark-users@xxxxxxxxxxxxx
To unsubscribe send an email to wireshark-users-leave@xxxxxxxxxxxxx