Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide
Appendix C Migrating From CTI OS 6.0
Migrating a C++ CIL application
C-2
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1)
Migrating a C++ CIL application
For a client application to be upgraded to use C++ CIL 7.1(1) the following tasks
need to be executed in order for the application to build with the new version.
need to be executed in order for the application to build with the new version.
Step 1
Port Build Project
Using your development environment utilities port your current application build
project to the new platform compatible with Microsoft C\C++ 7.1(1) and made all
the adjustments required by the vendor. For example, to port your Microsoft
Visual C++ 6.0 *.dsp project file to the new Microsoft Visual C++ 7.1(1) *.vcproj
format, open the *.dsp project selecting Open\ Project from the File command
menu in Microsoft Visual Studio .NET. For details refer to Microsoft’s Visual
Studio.NET help on Visual C++ Porting and Upgrading
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_
vc_porting_home.asp)
project to the new platform compatible with Microsoft C\C++ 7.1(1) and made all
the adjustments required by the vendor. For example, to port your Microsoft
Visual C++ 6.0 *.dsp project file to the new Microsoft Visual C++ 7.1(1) *.vcproj
format, open the *.dsp project selecting Open\ Project from the File command
menu in Microsoft Visual Studio .NET. For details refer to Microsoft’s Visual
Studio.NET help on Visual C++ Porting and Upgrading
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_
vc_porting_home.asp)
Step 2
Set New Compilation Parameters
a.
Remove all the references to stlport. With C++ CIL 7.1(1) the use of the
stlport templates library has been discontinued in favor of the standard
implementation now included in Visual C++ 7.1(1) and all the major C\C++
compiler distributions.
stlport templates library has been discontinued in favor of the standard
implementation now included in Visual C++ 7.1(1) and all the major C\C++
compiler distributions.
b.
Add _USE_NUMERIC_KEYWORDS=0 to the preprocessor definitions
setting for the C\C++ compiler settings. CTIOS 7.1(1) has been improved to
use a more efficient format for transmitting arguments arrays to and from
CTIOS Server. This definition is required by CIL C++ for its appropriate
performance. If not specified the application will behave in an unexpected
manner that can lead to a sudden halt or assertion.
setting for the C\C++ compiler settings. CTIOS 7.1(1) has been improved to
use a more efficient format for transmitting arguments arrays to and from
CTIOS Server. This definition is required by CIL C++ for its appropriate
performance. If not specified the application will behave in an unexpected
manner that can lead to a sudden halt or assertion.
c.
Add _WIN32_WINNT=0x0500 to the preprocessor definitions setting for the
C\C++ compiler settings. C++ CIL was build targeting the Win32 platform
so your application must be compiled for this platform only.
C\C++ compiler settings. C++ CIL was build targeting the Win32 platform
so your application must be compiled for this platform only.
d.
Disable 64-bit portability check options to avoid issues with pointers during
compilation. Microsoft Visual Studio.NET by default targets the Windows
XP platform that is enhanced to support 64-bit enabled applications. All the
libraries and code provided with Cisco CTIOS Toolkit 7.1(1) is targeted for
to the Win32 platform.
compilation. Microsoft Visual Studio.NET by default targets the Windows
XP platform that is enhanced to support 64-bit enabled applications. All the
libraries and code provided with Cisco CTIOS Toolkit 7.1(1) is targeted for
to the Win32 platform.
e.
Enable Buffer Security Check in the project Code Generation Settings