Getting error MSB4018 when trying to build wireshark sources

edit

I use the following settings:

set CYGWIN=nodosfilewarning   
set WIRESHARK_BASE_DIR=C:\wiresharkDev   
set WIRESHARK_TARGET_PLATFORM=win32   
set QT5_BASE_DIR=C:\Qt\Qt5.9.2\vcredist\vcredist_msvc2015_x86.exe   
set WIRESHARK_VERSION_EXTRA=-bella

What's wrong here?

You have the wrong path set in QT5_BASE_DIR. It should be C:\Qt\Qt5.9.2\msvc2015.

But there is no msvc2015 directory under C:\Qt\Qt5.9.2 What does it mean?

Somewhere under C:\Qt you should be able to find windeployqt.exe, that's usually in a "bin" directory. You need to set QT5_BASE_DIR to the directory above the "bin" directory.

For example I have (using Qt 5.9.1):

C:\Qt
  \5.9.1
    \msvc_2015    <--- set QT5_BASE_DIR to here.
      \bin
        \windeployqt.exe

Did you scratch your build dir and re ran cmake?

Well, I erased both wsbuild32 and wireshark-win32-libs directories and re-created wsbuild32.

After that I run cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 14 2015" ..\wireshark 2>&1 > cmake.txt and cmake.txt could be found here

Then I run msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln /t:Clean and after that msbuild /fl /flp:verbosity=diagnostic /m /p:Configuration=RelWithDebInfo Wireshark.sln msbuild.log is located here

Any idea?

Your CMake output looks OK.

The format of build output you are using is far too verbose, in addition it helps to turn off parallel builds (drop the /m) when debugging build output.

Please use msbuild /p:Configuration=RelWithDebInfo 2>&1 > build.txt to produce a build output file.

You can find build.txt file here: link text

Your build output looks OK, you should have a Wireshark.exe to test in C:\wiresharkDev\wsbuild32\run\RelWithDebInfo.

Interesting that I didn't do anything but dropped /m from the build command. And yes, now I have Wireshark.exe that tries to start and fails a second later.

I checked the stack,(not sure that it's ok) and it looks as follows:

software_update_init() line 109
WiresharkApplication::allSystemGo() line 1122
main line 845

and it looks like the problem is in these lines (in softwareupdateinit function):

if (strcmp(language, "system") != 0) {
        win_sparkle_set_lang(language);
}

Yep, that was a null pointer dereference that was fixed in change 24414. Update your sources to get the fix.

Thank you! Will try now But can you explain why the build is OK now after I dropped /m? What does his parameter do?

The /m allows multiple projects to be built in parallel across all the cores in your build machine. I use it all the time on my 4 core build VM's, as do the Wireshark build slaves (not sure how many cores they have) without issue. I remove it when debugging build output so that projects are then built in order and it's easier to read.

If the original answer has solved your problem (which was an incorrect Qt install) please accept it by clicking the "checkmark" icon.

The original answer did help me to find QT installation issue, but there are still weird issues related to original question - error MSB4018. I still cannot figure out what cause it why it disappeared after I dropped /m. And now - I rebuilt it with the NULL pointer fix and despite of the fact that I run it without /m the build failed with the same errors - new build.txt attached link text

Arguably this is a different question even if the symptoms are similar so should get a new one.

Anyway, the errors in your latest build relate to an inability to open zlib1.dll and what seems to be parallel build conflicts when building the docs. I'm uncertain why you get these, do you have wireshark open when building, or maybe it's caused by AV locking the files?

I also don't know why your subsequent build is attempting to rebuild the docs, it should be incremental, i.e. only what's changed. Are you doing a /t:clean between each build or adding /t:rebuild, if so neither should be required?

Well, after several iterations I can definitely tell that my original issue (error MSB4018 The "CustomBuild" task failed unexpectedly) is related to presence of /m flag.

If I run clean command without /m
msbuild /p:Configuration=RelWithDebInfo Wireshark.sln /t:Clean
and after that build command without /m as well:
msbuild /p:Configuration=RelWithDebInfo Wireshark.sln
everything works well. It makes me crazy, but at least the work-around found.

Anyway, thanks a lot for your great help!