Wireshark · Wireshark-dev: Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

On 19 June 2017 at 21:10, Maynard, Chris <Christopher.Maynard@xxxxxxx> wrote:

> Sigh. There is something really weird about my cygwin setup. I managed to get
> past the previous problems and now am hitting this:
>
>        "C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>        "C:\Development\wsbuild64\docbook\all_guides.vcxproj.metaproj"
> (default target) (3) ->
>        "C:\Development\wsbuild64\docbook\user_guides.vcxproj.metaproj"
> (default target) (30) ->
>        "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
> (default target) (32) ->
>        "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
> (default target) (119) ->
>          CUSTOMBUILD : I/O error : Attempt to load network entity
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>
> --
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)

For what it's worth, it might be useful to check the buildbot's environment.  For example, if you visit https://buildbot.wireshark.org/wireshark-master/waterfall then select the stdio link of the step of interest for the most similar buildbot to your system, you can check that buildbot's environment and output to see how it compares with your own.

Take Windows Server 2012 R2 x64, Build 3878 for example:

    -> ran CMake stdio: https://buildbot.wireshark.org/wireshark-master/builders/Windows%20Server%202012%20R2%20x64/builds/3878/steps/compile/logs/stdio
    -> compiled with MSBuild stdio: https://buildbot.wireshark.org/wireshark-master/builders/Windows%20Server%202012%20R2%20x64/builds/3878/steps/compile_1/logs/stdio

Hope that helps?  If not, I have a couple of batch files that I use to help me set up the environment and to build Wireshark that I could probably share?

One last tip to try is to remove Cygwin from your %PATH% prior to running cmake.  For me, having Cygwin in the %PATH% causes problems, so I remove it.
- Chris

+1 for this.  Having Cygwin on the path for Wireshark builds has always caused problems whenever I've encountered it and I've strongly recommended folks do NOT do this for a long time.

Another thing to note with CMake builds is that once CMake has located an external library or function call it will cache that info in CMakeCache.txt in the build directory and will never "forget" things (even if their path changes) unless you delete the entry in the file, or delete the file entirely. 

--

Graham Bloice