More info on issue: I seem to build from VS but not from command line. I put (to build in Win32)
!IFNDEF PLATFORM PLATFORM=WIN32!ENDIF Modified to !IFNDEF PLATFORM PLATFORM=x64!ENDIF (to build in x64) - And it worked. But only if I build from inside Visual Studio. I would like to be able to use a bat file (and build alll platform/configurations) The above - while it builds in VS, it will not build from command line (with commands: start /b /wait nmake -f makefile.vc clean start /b /wait nmake.exe /f makefile.vc PLATFORM=x64 start /b /wait nmake.exe /f makefile.vc devinstall PLATFORM=x64 The exact same thing builds in Win32... On Mon, May 13, 2013 at 8:53 AM, Mihaela Gaspar < [email protected]> wrote: > I am trying to build GDAL (1.9.2) in x64. > > In the instructions, I see: > > # Uncomment the following if you are building for 64-bit windows# (x64). > You'll need to have PATH, INCLUDE and LIB set up for 64-bit# compiles.!IF > "$(PLATFORM)" == "x64" > WIN64=YES!ENDIF > > And then, lower, > > # Under win64, symbols for function names lack the underscore prefix# present > on win32. Also the STDCALL calling convention is not used.!IFDEF WIN64!UNDEF > STDCALL!ELSE > SYM_PREFIX=_!ENDIF > > Can't find a PATH, INCLUDE and LIB specific for x64, or anything else > that I should do... > > I can build in Win32. > > In x64, I get linker errors: > > LINK : error LNK2001: unresolved external symbol _OGRFeatureStylePuller > LINK : error LNK2001: unresolved external symbol _OSRValidate... > gdal19.dll : fatal error LNK1120: 74 unresolved externals > > Please help. > > Thank you. > > > > -- *Mihaela Gaspar* *Urban Robotics Inc.** *Software Engineer 33 NW First Avenue, Suite 200 | Portland, OR 97209 c: 971-269-9649 [email protected] http://www.urbanrobotics.net
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
