|Getting Started with Pivotal GemFire Native Client / Running Native Client Applications|
GemFire uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on Windows, which invokes Microsoft® cl.exe from the command line at compile time.
The Pivotal GemFire native client 7.0 now supports .NET 4.0 and Visual Studio 2010. For advantages and more information on the features of .NET 4.0 and Visual Studio 2010 SP1, see http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx and http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx.
Visual Studio 2010 SP1 is the recommended compiler. If you are using any other compiler, contact technical support for assistance.
To build using the Microsoft Visual Studio Interface, from the Solutions Platform, choose Win32 or x86 from the Build menu for 32-bit builds or x64 for a 64-bit build.
The following table lists the compiler and linker switches that must be present on the cl.exe command line.
|/EHsc||Catches C++ exceptions only and tells the compiler to assume that *extern* C functions never throw a C++ exception.|
|/GR||Runtime type information.|
|-I%GFCPP%\include||Specifies the GemFire include directory.|
|%GFCPP%\lib\gfcppcache.lib||Specifies the library file for the shared library.|
|/D_CRT_SECURE_NO_DEPRECATE||Suppresses warnings. Required for Visual Studio 2010.|
|/D_CRT_NON_CONFORMING_SWPRINTFS||Suppresses warnings. Required for Visual Studio 2010.|
Because GemFire does not provide a library that can be linked statically into an application on Windows, you must dynamically link to the GemFire library.
To make the GemFire library available for loading, verify that the directory GemFireDir/bin is included in the PATH environment variable, where GemFireDir is the path to the GemFire product directory.