[Gdal-dev] problem compiling with VS.NET

Mateusz Łoskot mateusz at loskot.net
Fri Feb 24 18:09:09 EST 2006


Thom DeCarlo wrote:
> Hi,
> I just downloaded last night's tarball. Attempting to compile on WinXP with
> VS.NET 2003 very quickly yielded this:
> 
>         cl /nologo /MD /EHsc /Ox -I..\port -I..\ogr -I..\gcore  -I..\alg  /c
> cpl_vsi_mem.cpp
> cpl_vsi_mem.cpp
> cpl_vsi_mem.cpp(614) : error C3861: 'string': identifier not found, even
> with argument-dependent lookup
> NMAKE : fatal error U1077: 'cl' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio .NET
> 2003\VC7\BIN\nmake.exe"' : return code '0x2'
> Stop.
> 
> 
> Any idea why this is happening?

Hi Thom,

You're right. There was small bug, likely caused by my changes I made 
for Windows CE port.
I've just applied patch to the CVS repository.
Do clean checkout from CVS and it should work.
I've just tried to build GDAL with VC++ 7.1 and it compiles well.


If you don't want to do clean checkout, here is the patch.
Just replace the line marked with (-) with line marked with (+).
In case of any problem give me a note.


Index: port/cpl_vsi_mem.cpp
===================================================================
RCS file: /cvs/maptools/cvsroot/gdal/port/cpl_vsi_mem.cpp,v
retrieving revision 1.9
diff -u -a -r1.9 cpl_vsi_mem.cpp
--- port/cpl_vsi_mem.cpp	19 Feb 2006 21:54:34 -0000	1.9
+++ port/cpl_vsi_mem.cpp	24 Feb 2006 23:03:09 -0000
@@ -609,9 +609,8 @@
   */

  void VSIInstallMemFileHandler()
-
  {
-    VSIFileManager::InstallHandler( string("/vsimem/"),
+    VSIFileManager::InstallHandler( std::string("/vsimem/"),
                                      new VSIMemFilesystemHandler );
  }


-- 
Mateusz Łoskot
http://mateusz.loskot.net



More information about the Gdal-dev mailing list