#187 Can't build GLEW in Visual Studio 2010

1.10.0
closed
Nigel Stewart
None
8
2013-08-23
2012-05-04
Pehat
No

Your Visual Studio 6 project/solution files is a little bit out of date. After conversion of the solution into Visual Studio 2010 project and building I get error "LNK1181: cannot open input file '../../lib/glew32sd.lib". Please fix the project/solution files or suggest other solution.

Discussion

  • Nigel Stewart
    Nigel Stewart
    2012-05-08

    Confirming this. I can build each project individually, but rebuilding the entire solution fails.

    4>Build started 5/8/2012 5:39:02 PM.
    3>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(C:\nstewart\Downloads\glew-1.7.0\glew-1.7.0\build\vc6.../../bin\glewinfo.exe) does not match the Linker's OutputFile property value (C:\nstewart\Downloads\glew-1.7.0\glew-1.7.0\bin\glewinfod.exe). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
    3>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(glewinfo) does not match the Linker's OutputFile property value (glewinfod). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
    4>InitializeBuildStatus:
    4> Creating ".\static/debug\visualinfo.unsuccessfulbuild" because "AlwaysCreate" was specified.
    3>LINK : fatal error LNK1181: cannot open input file '../../lib/glew32sd.lib'
    3>
    3>Build FAILED.
    3>
    3>Time Elapsed 00:00:00.81
    4>ClCompile:
    4> visualinfo.c
    4>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(C:\nstewart\Downloads\glew-1.7.0\glew-1.7.0\build\vc6.../../bin\visualinfo.exe) does not match the Linker's OutputFile property value (C:\nstewart\Downloads\glew-1.7.0\glew-1.7.0\bin\visualinfod.exe). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
    4>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(visualinfo) does not match the Linker's OutputFile property value (visualinfod). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
    4>LINK : fatal error LNK1181: cannot open input file '../../lib/glew32sd.lib'
    4>
    4>Build FAILED.
    4>
    4>Time Elapsed 00:00:00.68
    ========== Rebuild All: 2 succeeded, 2 failed, 0 skipped ==========

     
  • Nigel Stewart
    Nigel Stewart
    2012-07-07

    I think the problem is that each configuration win32/win64 & debug/release needs to put files in independent places for the parallel build to work. I put VC10 projects in the git repo, but it needs more attention, I think.

     
  • Nigel Stewart
    Nigel Stewart
    2012-07-18

    VC10 projects are included in GLEW 1.8.0, now available.
    Batch build does not work, but project-by-project does work OK.
    This needs some more attention.

     


Anonymous


Cancel   Add attachments