This topic describes the settings for Microsoft Visual C++ you must use when compiling with the StreamBase C++ Client library to build StreamBase client applications and custom functions.
The header files, DLLs, and library files required to build native code for Windows are not delivered with the primary TIBCO StreamBase kit, but are instead delivered in a separate kit with its own installation package.
To develop C++ native code for Windows, after you install StreamBase, you must install the Windows Native SDK Package from
the installer file provided as a separate download from edelivery.tibco.com. In all cases, the installer file's name is in the form
release is the current StreamBase release number. Development in a .NET language does not require this kit.
When developing C++ native code for Windows using any of the supported compilers, specify the
<streambase/Client.hpp> header file in your code instead of the older
StreamBaseClient.hpp file. The
Client.hpp file identifies when the Visual C++ 10.0 compiler or newer versions of the compiler are in use and arranges for the correct,
compiler-specific version of the supporting libraries to be automatically loaded. For Visual C++ 9.0,
Client.hpp imports all the same definitions as
The following table describes the Visual C++ versions supported for building client applications and custom functions in C++ for StreamBase, to be hosted on Windows:
|StreamBase Extension||Visual C++ 10.0||Visual C++ 11.0|
|Client applications||can use||can use|
|Custom 64-bit functions for 64-bit Windows||must use||—|
StreamBase supports only 64-bit custom C++ native-code functions on Windows. Support for building 32-bit C++ functions was removed due to library changes that accompanied that release. See Building Custom C++ Functions on Windows for suggestions for migrating any 32-bit C++ functions you may have written for older StreamBase releases.
When developing a client or server monitor application in a .NET language, you can use either Visual Studio 2012 or 2013, as described in Creating .NET Clients.
The next table clarifies the relationship between Microsoft Visual Studio product names and Visual C++ versions:
|Visual C++ Version||Visual Studio Name|
|Visual C++ 10.0||part of Visual Studio 2010|
|Visual C++ 11.0||part of Visual Studio 2012|