Very strange linking issue

  • Thread starter Thread starter wbierman808
  • Start date Start date
W

wbierman808

Guest
Hello. My basic situation is this:

  • Visual Studio 2015 Version 14.0.25123.00 Update 2.
  • I have five projects in one solution.
  • Three are static .lib projects, and two are exes.
  • Both executables link all three static .libs.
  • One executable links successfully, and one does not.
  • The one that does not compile says it cannot find a .lib and errors.
  • If I remove that .lib requirement, the next ones cannot be found either. It is finding none of them.
  • I have repeatedly confirmed that the paths and settings for the non-linking executable project are correct and identical to the settings for the project which links successfully.
  • I have tried recreating the project for the non-linking executable from scratch and have the same problem.
  • In the non-linking executable's project, whenever I add a project reference, it is listed under References with a yellow triangle and an exclamation mark.
  • If I view the properties for one of these broken references, the 'Full Path' contains the following string: "The "Microsoft.VisualStudio.ProjectSystem.References.UnresolvedBuildDependencyProjectReference" reference could not be resolved."
  • The Assembly Name property is empty in those same properties.
  • If I view the properties for the same reference in the linking project, the Assembly Name property is correct, as is the path to the .lib file in 'Full Path'.
  • I have tried manually executing link.exe, and even that does not work. It says that the .lib file(s) cannot be found.

I can provide any other information that might be necessary. Please help me!

Continue reading...
 
Back
Top