[vtkusers] Using debugging lib with MSVC

[Andrew J. P. Maclean]

I use the debug versions without any problems. It seems to me that it
may be a compiler setting. Check the project settings to make sure that
C++ is used (and not C) Generally this is the case if CPP is the
extension. Also try switching off the precompiled header settings and
see if this works.

___________________________________________
Andrew J. P. Maclean
Postal:
Australian Centre for Field Robotics
The Rose Street Building J04
The University of Sydney  2006  NSW
AUSTRALIA
Room:
106
Phone:
+61 2 9351 3283
Fax:
+61 2 9351 7474

http://www.acfr.usyd.edu.au/
___________________________________________


-----Original Message-----
From: Johnny Norris [mailto:jnorris at mcs.anl.gov] 
Sent: Sunday, 2 September 2001 04:27
To: Vtk Mailing List
Subject: [vtkusers] Using debugging lib with MSVC

Hi,

I'm trying to compile my application with debugging information under
Windows 2000 using MS Visual C++ 6.0.  I've compiled the debug version
of
VTK without any problems, but whenever I try to compile a source file
that
includes a VTK header, I always get errors like the following:

../../../vtk/common\vtkObject.h(117) : error C2059: syntax error :
'string'
../../../vtk/common\vtkObject.h(117) : error C2091: function returns
function
../../../vtk/common\vtkObject.h(117) : error C2802: static member
'operator new' has no formal parameters
../../../vtk/common\vtkObject.h(118) : error C2059: syntax error :
'string'
../../../vtk/common\vtkObject.h(118) : error C2091: function returns
function
../../../vtk/common\vtkObject.h(118) : error C2556: 'void *(__cdecl
*__cdecl vtkObject::operator new(void))(unsigned int)' : overloaded
function differs only by return type from 'void *(__cdecl *__cdecl
vtkObject::operator new(void))(unsigned int,co
nst char *,int)'
        ../../../vtk/common\vtkObject.h(117) : see declaration of 'new'

Compiling a release version works fine.  I've checked that the compiler
flags
and defines are the same, but nothing I've done has been able to fix it.
I'm
using a nightly release of VTK from the end of July.

Has anyone else had a problem like this?

Thanks,
John
-- 
John Norris
Research Programmer
Center for Simulation of Advanced Rockets
http://www.uiuc.edu/ph/www/jnorris