Ошибка lnk1181 не удается открыть входной файл

asked Jul 10, 2013 at 22:17

I solved the issue by renaming the .obj files without their file extension. For example, it was looking for file name «foo», I had «foo.obj» so I renamed «foo.obj» to «foo».

asked Jul 10, 2013 at 22:17

I solved the issue by renaming the .obj files without their file extension. For example, it was looking for file name «foo», I had «foo.obj» so I renamed «foo.obj» to «foo».

I’ve been encountering a strange bug in Visual Studio 2010 for some time now.

I have a solution consisting of a project which compiles to a static library, and another project which is really simple but depends on this library.

Sometimes, in the last days extremely frequent, after Rebuilding the Solution or just compiling it with 1-3 changed source files, I get the following error:

2>LINK : fatal error LNK1181: cannot open input file 'thelibrary.lib'
========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========

Where compiling thelibrary.lib was a success without any errors or warnings.

I have tried cleaning the solution, but that doesn’t always work.

• What is wrong here?

answered Jun 25, 2012 at 2:19

I can see only 1 things happening here:
You did’t set properly dependences to thelibrary.lib in your project meaning that thelibrary.lib is built in the wrong order (Or in the same time if you have more then 1 CPU build configuration, which can also explain randomness of the error). ( You can change the project dependences in: Menu->Project->Project Dependencies )

I solved it with the following:

Go to View-> Property Pages -> Configuration Properties -> Linker -> Input

Under additional dependencies add the thelibrary.lib. Don’t use any quotations.

answered Feb 7, 2013 at 3:08

I had a similar problem in that I was getting LINK1181 errors on the .OBJ file that was part of the project itself (and there were only 2 .cxx files in the entire project).

Initially I had setup the project to generate an .EXE in Visual Studio, and then in the
Property Pages -> Configuration Properties -> General -> Project Defaults -> Configuration Type, I changed the .EXE to .DLL. Suspecting that somehow Visual Studio 2008 was getting confused, I recreated the entire solution from scratch using .DLL mode right from the start. Problem went away after that. I imagine if you manually picked your way through the .vcproj and other related files you could figure out how to fix things without starting from scratch (but my program consisted of two .cpp files so it was easier to start over).

I’m stumbling into the same issue. For me it seems to be caused by having 2 projects with the same name, one depending on the other.

For example, I have one project named Foo which produces Foo.lib. I then have another project that’s also named Foo which produces Foo.exe and links in Foo.lib.

I watched the file activity w/ Process Monitor. What seems to be happening is Foo(lib) is built first—which is proper because Foo(exe) is marked as depending on Foo(lib). This is all fine and builds successfully, and is placed in the output directory—$(OutDir)$(TargetName)$(TargetExt). Then Foo(exe) is triggered to rebuild. Well, a rebuild is a clean followed by a build. It seems like the ‘clean’ stage of Foo.exe is deleting Foo.lib from the output directory. This also explains why a subsequent ‘build’ works—that doesn’t delete output files.

A bug in VS I guess.

Unfortunately I don’t have a solution to the problem as it involves Rebuild. A workaround is to manually issue Clean, and then Build.

answered Apr 25, 2013 at 5:26

answered Dec 3, 2013 at 7:56

Maybe you have a hardware problem.

I had the same problem on my old system (AMD 1800 MHz CPU ,1GB RAM ,Windows 7 Ultimate) ,until I changed the 2x 512 MB RAM to 2x 1GB RAM. Haven’t had any problems since. Also other (minor) problems disappeared. Guess those two 512 MB modules didn’t like each other that much ,because 2x 512 MB + 1GB or 1x 512 MB + 2x 1GB didn’t work properly either.

answered Jun 24, 2011 at 8:09

answered Oct 17, 2014 at 12:54

You can also fix the spaces-in-path problem by specifying the library path in DOS «8.3» format.

To get the 8.3 form, do (at the command line):

DIR /AD /X

recursively through every level of the directories.

answered Jun 4, 2016 at 22:15

I had the same problem. Solved it by defining a macro OBJECTS that contains all the linker objects e.g.:

OBJECTS = target.exe kernel32.lib mylib.lib (etc)

And then specifying $(OBJECTS) on the linker’s command line.

I don’t use Visual Studio though, just nmake and a .MAK file

I had the same error when running lib.exe from cmd on Windows with a long argument list. apparently cmd.exe has max line length of about 8K characters, which resulted that the filenames at the end of this threshold got changed, thus resulting in bad filename error.
my solution was to trim the line. I removed all paths from filenames and added single path using /LIBPATH option. for example:

/LIBPATH:absolute_path /OUT:outfilename filename1.obj filename2.obj ... filenameN.obj

answered Nov 1, 2018 at 14:31

I found a different solution for this…

Actually, I missed comma separator between two library paths. After adding common it worked for me.

Go to: Project properties -> Linker -> General -> Link Library Dependencies
At this path make sure the path of the library is correct.

Previous Code (With Bug — because I forgot to separate two lib paths with comma):

<Link><AdditionalLibraryDirectories>....Buildlib$(Configuration)**....BuildRelease;**%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>

Code after fix (Just separate libraries with comma):

<Link><AdditionalLibraryDirectories>....Buildlib$(Configuration)**;....BuildRelease;**%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>

Hope this will help you.

In my case I had the library installed using NuGet package (cpprestsdk) AND I falsely added the lib to the Additional Dependancies in the Linker settings. It turns out, the package does it all for you.

The linker then tried to find the library in the library path and of course could not find it.

After removing the library from the Additional Dependencies everything compiled and linked fine.

answered May 10, 2019 at 11:35

Not quite the answer to OP’s question as I am using CMake with Visual Studio as a generator but I personally also just encountered the same issue (I am using Visual Studio toolchain, but not the IDE to build stuff).

My fix was target linking the directory of the directory of the libraries (I had a few) before target linking the library.

//Works
target_link_directories(MyExe PRIVATE /out/of/scope/path/to/lib)
foreach(X IN LISTS LIBSLISTNAMES)
    target_link_libraries(MyExe ${X})
endforeach()

//Throws cannot open cannot open input file error
 foreach(X IN LISTS LIBSLISTNAMES)
    target_link_libraries(MyExe /out/of/scope/path/to/lib/${X})
endforeach()

Not sure what is happening under the hood, but maybe VS IDE has equivalent setting somewhere?

answered Jun 17, 2021 at 0:36

I’ve also experienced this problem. For me the dependencies were properly set, but one of the projects in my solution wasn’t selected for building in the configuration (VS 2022 pro).

I eventually figured out thanks to output in Build -> Clean Solution that mentioned one of the project in dependency chain being disabled. Interesingly enough, when trying to build the disabled project it wouldd not properly build its dependencies.

answered Feb 14, 2022 at 15:14