[vtk-developers] borland developer studio 2006

[Luca Picello]

Hello Mathieu,
the new environment is officially still in preview. lots of bugs still in...
however i'm particulary happy we can continue with bcb full RAD power!! :-)
the petition to borland to force to be vtk compliant has not been 
forgotten. but we do need all your support (bcb developers).

Borland C++ 5.8 for Win32 Copyright (c) 1993, 2005 Borland
Z:\VTK\Utilities\DICOMParser\DICOMAppHelper.cxx:
Error E2268 Z:\VTK\Utilities\DICOMParser\DICOMAppHelper.cxx 588: Call to 
undefined function 'memcpy' in function 
DICOMAppHelper::ImagePositionPatientCallback(DICOMParser *,unsigned 
short,unsigned short,DICOMParser::VRTypes,unsigned char *,int)
Error E2268 Z:\VTK\Utilities\DICOMParser\DICOMAppHelper.cxx 610: Call to 
undefined function 'memcpy' in function 
DICOMAppHelper::ImagePositionPatientCallback(DICOMParser *,unsigned 
short,unsigned short,DICOMParser::VRTypes,unsigned char *,int)
*** 2 errors in Compile ***

bcb2006.bugs->add( "memcpy is defined in <mem.h> only, even if bds2006 
documentation reports <string.h>.")
See ya,
Luca



Mathieu Malaterre wrote:

> Luca Picello wrote:
>
>> I've had a try with new Borland Developer Studio 2006 which includes 
>> the new BorlandC++ Builder compiler.
>> Now the latest cvs can be again compiled successfully with non-free 
>> bcb in dynamic-library mode. in the next few days i'll make a try to 
>> examples, tests, tcl and static libraries too.
>>
>> compiler: Borland C++ 5.8 for Win32 Copyright (c) 1993, 2005 Borland
>> linker: Turbo Incremental Link 5.69 Copyright (c) 1997-2005 Borland
>>
>> only Utilities/DICOMParser/DICOMAppHelper.cxx has been modified at 
>> the moment adding
>> #include <mem.h>
>
>
> Luca,
>
>     This would really be nice if we could patch VTK to support this 
> new borland compiler. Unfortunately I need to know the exact error you 
> got when compiling VTK. Indeed the mem.h file is not POSIX and cannot 
> be included in an uniform way.
>
> Thanks for your help
> Mathieu
> .
>