My wild guess. Somewhere you have a spaces-in-name shit and a code named (some variation of this) "lib thisprogram.cpp" got truncated and the linker is now searching for the lib.obj instead of "lib thisprogram.obj"
Joaquim -----Original Message----- From: gdal-dev <gdal-dev-boun...@lists.osgeo.org> On Behalf Of Jeff McKenna Sent: Friday, November 12, 2021 3:14 PM To: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Building Gdal with C++ Visual Studio 2019 - Error Linking. Please also see the BuildHints wiki, as many of us were contributing there steps for Windows and other GDAL drivers over the years: https://trac.osgeo.org/gdal/wiki/BuildingOnWindows. Today it's still a gold mine of tips and configure steps that are key to making it all work together. -jeff -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ On 2021-11-11 6:39 p.m., peter vG via gdal-dev wrote: > I've been trying to build the binaries for Gdal 3.3.3 (and 3.4.0) using > Visual C++ (via Visual Studio 2019), but I am getting a linking error > that has me scratching my head: LINK : "fatal error LNK1104: cannot open > file 'C:\gdal-3.4.0\lib.obj'". What is lib.obj? I am new to Visual C++, > having come from the CPP Builder world, so I'm still getting my head > around this product. Any suggestions would be greatly appreciated as I > am wasting my life trying to hunt down a solution! > > _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev