I have fatal error LNK1181 when rebuild wireshark on Window

fatal
retag add tags

I am trying follow this instruction to build Wireshark on window: https://www.wireshark.org/docs/wsdg_h...

The build was successful and I was be able to run Wireshark.exe, so I started to follow this instruction to add the plugins for wireshark: https://blog.fjh1997.top/2019/03/29/s...

But after follow each steps, my plugins does not show the foo.ddl, I thought that I did something wrong for configuration of the plugins, so I decided to delete the build directory and build wireshark again just to make sure.

After doing everything I did the first time I built, it show this error:

 Build FAILED.

   "C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
   "C:\Development\wsbuild64\wireshark.vcxproj.metaproj" (default target) (2) ->
   "C:\Development\wsbuild64\wireshark.vcxproj" (default target) (147) ->
   (Link target) ->
     LINK : fatal error LNK1181: cannot open input file 'C:\Development\wsbuild64\ui\qt\qtui.dir\RelWithDebInfo\mocs_compilation_Debug.obj' [C:\Development\wsbuild64\wireshark.vcxproj]

0 Warning(s)
1 Error(s)

I have tried to clean and then recompile again, but it still showing errors. So I decided to delete the directory, try to build it once more time, but unfortunately I still got this error and I do not know why. Can someone help me? I really appreciate, this is my first time working with Wireshark.

Edit: When I open folder C:\Development\wsbuild64\ui\qt\qtui.dir\RelWithDebInfo\ as shown in the error, there is no mocs_compilation_Debug.obj, does this mean that I am missing 1 file? Is there any way I can add it?

huong

asked 2021-05-07 08:46:45 +0000, updated 2021-05-07 09:01:45 +0000

edit flag offensive 0 remove flag close merge delete

Comments

Are you building with sources from git, or from a tarball? What is the git commit or version of the tarball?

grahamb (2021-05-07 09:30:57 +0000) edit

Hi, I am building source from git, just like in the instruction from wireshark: git clone https://gitlab.com/wireshark/wireshark.git

huong (2021-05-07 09:46:02 +0000) edit

OK, it works for me and the buildbots, so is likely to be something local in your environment. Just be aware that when living on the bleeding edge of master that there may be occasional unintentional breakages. You can also check the buildbots to see if they can build: https://buildbot.wireshark.org/wiresh...

I'm not sure if you have done this but think you should try the "nuclear" option of deleting the build directory and generating a new build solution, preferably without your additions, and when that's working move on to adding the plugin.

grahamb (2021-05-07 10:06:28 +0000) edit

yes thank you for your comment, I deleted the build directory and try once again but it still occurs the same error, maybe there is something in my environment, I will check and see if I installed everything before right. It just really confusing because it worked before.

huong (2021-05-07 10:35:01 +0000) edit

Do you have all the required env vars setup correctly?

grahamb (2021-05-07 10:52:25 +0000) edit

add a comment see more comments

2 Answers

Sort by

oldest

newest

most voted

This should be fixed in https://gitlab.com/wireshark/wireshar....

3.5k

Gerald Combs

answered 2021-05-14 01:09:22 +0000

edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

Hi, I have solved the problem but I do not know why it occurred. The problem was that in wireshark.vcxproj file, it is trying to find the mocs_compilation_Debug.obj file.

But in my case, there is no such file in C:\Development\wsbuild64\ui\qt\qtui.dir\RelWithDebInfo direction, there is only file mocs_compilation_RelWithDebInfo.obj

So I replace the name of mocs_compilation_Debug.obj with mocs_compilation_RelWithDebInfo.obj, then the cmake runs fine, and wireshark application is built. Although I do not understand the real problem behinds it, but I hope this will work well.

huong

answered 2021-05-10 08:43:11 +0000

11.1k

cmaynard

updated 2021-05-12 21:30:45 +0000

edit flag offensive 0 remove flag delete link

Comments

You've fixed the immediate issue, but without finding out how the errant information was inserted (presumably by the CMake generation step) you may run into the problem again.

grahamb (2021-05-10 09:02:37 +0000) edit

You may have to include the qt debug info in your qt setup. Has to be explisitly downloaded if I remember correctly.

Anders (2021-05-10 09:13:17 +0000) edit

If the Qt PDBs are missing this usually just causes a link warning. In this case the CMake generated .vcxproj has errant info where the locally compiled object file has a strange name.

grahamb (2021-05-10 10:05:37 +0000) edit

I've encountered this exact same problem after upgrading CMake from 3.19.8 to 3.20.2. I was going to downgrade back to 3.19.8, but I don't have time to do that today. @huong, what version of CMake are you running? If it's 3.20.x, you might want to try 3.19.8 to see if that resolves the problem.

NOTE: I do not experience this problem with 3.4.5 sources and CMake 3.20.2, only with master, so I don't think this is a CMake problem, per se.

cmaynard (2021-05-12 21:29:07 +0000) edit

Related to these?
Build fails with CMake 3.20
CMake: Enable AUTO{MOC,UIC,RCC} for the qtui target explicitly.

The Developer Guide doesn't specify a version.
Wiki lists 3.19.2 and the Buildbot is using Generating build using CMake 3.19.6

Chuckc (2021-05-12 21:50:36 +0000) edit

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer

I have fatal error LNK1181 when rebuild wireshark on Window edit

Comments

2 Answers

Comments

Comments