That was exactly it, thanks very much Tamas.
-jeff
Tamas Szekeres wrote:
Jeff,
I'm guessing you're linking against an incorrect version of setargv.obj.
I see the Win64 version can be found in:
C:\Program Files (x86)\Microsoft Visual Studio 8\VC\lib\amd64
if you use VC2008 for example.
Best regards,
Tamas
2009/3/6 Jeff McKenna <[email protected]
<mailto:[email protected]>>
I am building a 64-bit GDAL on a 32-bit windows machine, and
enabling setargv throws this GDAL error when compiling:
*********
cd apps
nmake /nologo /f makefile.vc <http://makefile.vc>
cl /nologo /MD /EHsc /Ox /W3 /D_CRT_SECURE_NO_DEPRECATE
/D_CRT_NONSTDC_N
O_DEPRECATE /DNDEBUG -I..\port -I..\ogr -I..\gcore -I..\alg
-I..\ogr\ogrsf_frmt
s -I..\frmts -I..\alg -I..\ogr -I..\ogr\ogrsf_frmts
gdal_translate.cpp "D:\So
ftware\MICROS~1.0\VC\lib\setargv.obj" ..\gdal_i.lib /link
gdal_translate.cpp
D:\Software\MICROS~1.0\VC\lib\setargv.obj : fatal error LNK1112:
module machine
type 'X86' conflicts with target machine type 'x64'
NMAKE : fatal error U1077: '"D:\Software\Microsoft Visual Studio
9.0\VC\BIN\x86_
amd64\cl.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"D:\Software\Microsoft Visual Studio
9.0\VC\BIN\nmak
e.EXE"' : return code '0x2'
Stop.
**********
If I don't enable setargv GDAL 64-bit compiles fine (using today's
GDAL trunk). (I have set GDAL's "WIN64" flag)
Any ideas why this error is happening?
-jeff
--
Jeff McKenna
FOSS4G Consulting and Training Services
http://www.gatewaygeomatics.com/
_______________________________________________
gdal-dev mailing list
[email protected] <mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/gdal-dev
--
Jeff McKenna
FOSS4G Consulting and Training Services
http://www.gatewaygeomatics.com/
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev