Why does fatal error LNK1104 cannot open file C Program obj occur when I compile a C project in Visual Studio

Question

I ve created a new C   project in Visual Studio 2008   No code has been written yet   Only project settings have been changed   When I compile the project  I receive the following fatal error      fatal error LNK1104  cannot open file  C  Program obj

User · Answer

I solved it by adding an existing project to my solution  which I forgot to add in the first time

User · Answer

I had this exact error when building a VC   DLL in Visual Studio 2019      LNK1104  cannot open file  C  Program obj    Turned out under project Properties   Linker   Input   Module Definition File  I had specified a def file that had an unmatched double-quote at the end of the filename   Deleting the unmatched double quote resolved the issue

User · Answer

I had the same problem  but solution for my case is not listed in answers  My antivirus program  AVG  determined file MyProg exe as a virus and put it into the  virus storehouse   You need to check this storehouse and if file is there - then just restore it  It helped me out

User · Answer

I tried above solution but didnt work for me  So i rename the exe and rebuild the solution  It works for me

User · Answer

My issue was caused by other application using the  dll file I was trying to debug  Closing the application that was using the  dll solved it for me

User · Answer

I had the same problem It caused by a     in the name of a folder of additional library path It solved by changing the additional library path

User · Answer

I had this issue in conjunction with the LNK2038 error  followed this post to segregate the RELEASE and the DEBUG DLLs  In this process I had cleaned up the whole folder where these dependencies were residing   Luckily I had a backup of all these files  and got the file for which this error was throwing back into the DEBUG folder to resolve the issue  The error code was misleading in some way as I had to spend a lot of time to come to this tip from one of the answers from this post again   Hope this answer  helps someone in need

User · Answer

I m answering because I don t see this particular solution listed by anyone else   Apparently my antivirus  Ad-Aware  was flagging a DLL one of my projects depends on  and deleting it  Even after excluding the directory where the DLL lives  the same behaviour continued until I restarted my computer

User · Answer

My problem was a missing  lib extension  I was just linking against mylib and VS decided to look for mylib obj

User · Answer

In my case  I had replaced math library files from a previous Game Engine Graphics course with GLM  The problem was that I didn t add them to the project within Visual Studio s Solution Explorer  even though they were in the project repository

User · Answer

I had the same error  just with a Nuget package i had installed  one that is not header only  and then tried to uninstall  What was wrong for me was that i was still including a header for the package i just uninstalled in one of my  cpp files  pretty silly  yes   I even removed the additional library directories link to it in Project - gt  Properties - gt  Linker - gt  General  but of course to no avail since i was still trying to reference the non-existent header     Definitely a confusing error message in this case  since the header name was  lt boost filesystem hpp gt  but the error gave me  cannot open file  llibboost filesystem-vc140-mt-gd-1 59 lib   and no line numbers or anything

User · Answer

I had the same error    fatal error LNK1104  cannot open file  GTest lib     This was caused by the   at the end  If you have multiple libraries  they should be separated by empty space  spacebar   no comma or semi-colons    So don t use   or any anything else when listing libraries in Project properties    Configuration Properties    Linker    Input

User · Answer

I hit the same problem with  Visual Studio 2013     LNK1104  cannot open file  debug      exe   It resolved after closing and re-starting Visual studio

User · Answer

For an assembly project  ProjectName -  Build Dependencies -  Build Customizations -  masm  selected    setting Generate Preprocessed Source Listing to True caused the problem for me too  clearing the setting fixed it  VS2013 here

User · Answer

in my case it was the path lenght  incl  file name                        SWX Binary VS2008 Output Win32 Debug boost unit test framework-vc90-mt-gd-1 57 lib   as for the release the path was  this has worked correctly                        SWX Binary VS2008 Output Win32 Release boost unit test framework-vc90-mt-1 57 lib      gt  one char shorter   i have also verified this by renaming the lib file  using shorter name  and changing this in the  Linker - gt  input - gt  additoinal dependencies  i have also verified this by adding absolut path instead of relative path as all those  quot    quot  has extended the path string  too  this has also worked   so the problem for me was the total size of the path   filename string was too long

User · Answer

Check also that you don t have this turned on  Configuration Properties -  C C   -  Preprocessor -  Preprocess to a File

User · Answer

Killed msbuild32 exe and built again  It worked for me

User · Answer

I run into the same problem with linker complaining about the main executable missing  This happened during our solution port to the new Visual Studio 2013  The solution is a varied mix of managed and un-managed projects code  The problem  and fix  ended up being a missing app config file in the solution folder  Took a day to figure this one out     as output log was not very helpful

User · Answer

This can happen if the file is still running as well       -1  error  LNK1104  cannot open file  debug      exe

User · Answer

In my case it was a matter of a mis-directed reference   Project referenced the output of another project but the latter did not output the file where the former was looking for

User · Answer

I was having the same problem   I have just copied the code to new project and started the build    Some other error started coming   error C4996   fopen   This function or variable may be unsafe  Consider using fopen s instead  To solve this problem again  I have added my one property in the Project project as below   Project -  Properties -  Configuration property -  c c      In this category there is field name Preprocessor Definitions I have added  CRT SECURE NO WARNINGS this to solve the problem Hope it will help      Thank You

User · Answer

The problem went away for me after closing and re-opening Visual Studio  Not sure why the problem happened  but that might be worth a shot   This was on VS 2013 Ultimate  Windows 8 1

User · Answer

I checked all my settings according to this list  http   msdn microsoft com en-us library ts7eyw4s aspx feedback   It is helpful to me and for my situation  I find out that Link Dependency of projects  properties has double-quote  which should not be there

User · Answer

This particular issue is caused by specifying a dependency to a lib file that had spaces in its path   The path needs to be surrounded by quotes for the project to compile correctly   On the Configuration Properties -  Linker -  Input tab of the project   s properties  there is an Additional Dependencies property   This issue was fixed by changing this property from      C  Program Files sofware   sdk lib library lib   To        C  Program Files sofware   sdk lib library lib    Where I added the quotes

User · Answer

Solution 1  for my case   restart windows Explorer process  yes  the windows file manager    Solution 2    Close Visual Studio  Windows Logoff Logon  reopen Visual Studio Build as usual  It now builds and can access the problematic file    I presume sometimes the file system or whoever is controlling it gets lost with its permissions  Before restarting the windows session  tried to kill zombie msbuild32 exe processes  restart visual studio  check none even showing the problem file on  No build configuration issues  It happens now and then  Some internal thing in Windows does not fix up  needs a restart

[visual-c++] Why does fatal error "LNK1104: cannot open file 'C:\Program.obj'" occur when I compile a C++ project in Visual Studio?

Examples related to visual-c++

Examples related to linker