\r
-DDK (Driver Development Kit) Build Environment Example [12-06-07]\r
+WDK (Windows Driver Kit) Build Environment Example [4-08-10]\r
-----------------------------------------------------------------\r
\r
-Install the Windows Server 2003 (SP1) DDK see\r
-http://www.microsoft.com/whdc/devtools/ddk/default.mspx .\r
+Install the Windows WDK see\r
+ http://www.microsoft.com/whdc/Devtools/wdk/default.mspx\r
\r
-Why use the DDK? Windows Server 2003 DDK (SP1) is what's used to build the WinOF\r
+Why use the WDK? WDK (600.16385.0) is what's used to build the OFED for Windows\r
distribution.\r
-Installing the DDK first requires burning a CD of the downloaded DDK - sigh...\r
+Installing the WDK first requires burning a CD of the downloaded WDK - sigh...\r
\r
-Due to the problematic nature of spaces in path names, Windows Server 2003 DDK\r
-does not allow spaces in pathnames; this is why IBSDK is not installed under\r
-WinOF.\r
+Due to the problematic nature of spaces in path names, the Windows Driver Kit\r
+does not allow spaces in pathnames; Due to the spaces in %ProgramFiles%\OFED\r
+path, the OFED_SDK is not installed under %ProgramFiles%\OFED.\r
+See %SystemDrive%\OFED_SDK\\r
\r
\r
Building CM test example\r
------------------------\r
\r
-Start a 'Free/Release' type DDK command prompt for you respective architecture [x86,amd64,ia64].\r
+Start a 'Free/Release' type WDK command window for you respective architecture\r
+[x86,amd64,ia64]; assumed OS is Windows Server 2008 R2 (aka win7).\r
\r
-cd to C:\IBAL\Sampes\DDK\r
+cd to %SystemDrive%\OFED_SDK\Samples\DDK\r
\r
-Set the 'OPENIB_REV' env variable to the svn version number.\r
-Hold the mouse-point over the file 'C:\Program Files (x86)\WinOF\opensm.exe'.\r
+Set the 'OPENIB_REV' env variable to the svn version number; any # will work.\r
+Hold the mouse-point over the file 'C:\Program Files\OFED\opensm.exe'.\r
The last field of the 'File Version' field is the svn revision number.\r
\r
-set OPENIB_REV=917\r
+example: set OPENIB_REV=917\r
\r
-If building an 32-bit cmtest version on an x64 platform, edit Sources file by adding '32' to\r
-ibal.lib and complib.lib, resulting in 'ibal32.lib' and 'complib32.lib'.\r
-Note - executable will be appear as 'objfre_wnet_x86\i386\cmtest.exe'.\r
+If building an 32-bit cmtest version on an x64 platform, edit Sources file by\r
+adding '32' to ibal.lib and complib.lib, resulting in 'ibal32.lib' and\r
+'complib32.lib'.\r
+Note - executable will be appear as 'objfre_win7_x86\i386\cmtest.exe'.\r
\r
-build -wg\r
+build /wg\r
\r
The executable will be created in a processor specific directory:\r
\r
x64 (Release/Free) example:\r
- C:\IBAL\Sampes\DDK\objfre_wnet_amd64\amd64\cmtest.exe\r
+ %SystemDrive%\OFED_SDK\Samples\DDK\objfre_win7_amd64\amd64\cmtest.exe\r
\r
x64 (Checked/Debug)) example:\r
- C:\IBAL\Sampes\DDK\objchk_wnet_amd64\amd64\cmtest.exe\r
+ %SystemDrive%\OFED_SDK\Samples\DDK\objchk_win7_amd64\amd64\cmtest.exe\r
\r
x86 (Release/Free) example:\r
- C:\IBAL\Sampes\DDK\objfre_wnet_x86\i386\cmtest.exe\r
+ %SystemDrive%\OFED_SDK\Samples\DDK\objfre_win7_x86\i386\cmtest.exe\r
\r
Executing cmtest.exe\r
--------------------\r
\r
Note: <spaces> are not allowed between command line switch and it's argument.\r
\r
-Server side: cmtest -s -l0xlll -r0xrrr -m1024 -n100\r
+Server side: cmtest -s -l0xlll -r0xrrr -m1024 -n100\r
\r
Client side: cmtest.exe -l0xlll -r0xrrr -m1024 -n100\r
\r
# \r
# NMAKE Options (passed as macro) \r
#\r
-# Select a Visual Studio 2005 command window from the start menu\r
+# Select a Visual Studio command window from the start menu\r
# vcvarsall X64 - sets X64 processor compilation env, X86 | IA64\r
#\r
#*********************************************************************/\r
\r
SRC=cmtest\r
\r
-LIB_PATH=C:\IBSDK\Lib\r
-INC_PATH=C:\IBSDK\Inc\r
+LIB_PATH=C:\OFED_SDK\Lib\r
+INC_PATH=C:\OFED_SDK\Inc\r
\r
IB_LIBS=ibal.lib complib.lib\r
\r
\r
LINK = link\r
\r
-LIBS = ws2_32.lib advapi32.lib User32.lib bufferoverflowU.lib\r
+LIBS = ws2_32.lib advapi32.lib User32.lib\r
\r
LINK_FLAGS = /nologo /subsystem:console /machine:$(ARCH) $(LIBS) \\r
/libpath:$(LIB_PATH) $(IB_LIBS)\r
\r
-Visual Studio 8/5.0 (C++) Build Environment [12-06-07]\r
+Visual Studio (C++) Build Environment [4-07-10]\r
-----------------------------------------------------------------\r
\r
-Install Microsoft Visual Studio 8/5.0 (C++ env)\r
+Install Microsoft Visual Studio 10 (C++ env)\r
\r
\r
**** WARNING - win32 application building ****\r
\r
-The Visual Studio default calling convention is '__cdecl' (/Gd).\r
+Disregard if building x64 application.\r
+\r
+The Visual Studio default x86 calling convention is '__cdecl' (/Gd).\r
The 32-bit versions of ibal32.lib & complib32.lib are built using '__stdcall'\r
as the default calling convention (AL_API & CL_API).\r
Make _sure_ 'all' user-defined ibal and complib callback routines match the\r
convention for your 'win32' InfiniBand application.\r
\r
\r
-Building CM test example\r
-------------------------\r
+Building CM test example from a cmd.exe window\r
+----------------------------------------------\r
\r
\r
-cd to C:\IBAL\Samples\VS\r
+cd to %SystemDrive%\OFED_SDK\Samples\VS\r
\r
\r
Makefile Solution\r
\r
Salient Solution points:\r
compile as a C program\r
- set additional Include path as C:\IBSDK\Inc\r
- set additional Resource Include path as C:\IBSDK\Inc\r
- Set additional Library path as C:\IBSDK\Lib .\r
+ set additional Include path as C:\OFED_SDK\Inc\r
+ set additional Resource Include path as C:\OFED_SDK\Inc\r
+ Set additional Library path as C:\OFED_SDK\Lib .\r
Link with additional libraries ibal.lib & complib.lib .\r
If building a win32 application on a 64-bit platform then link with\r
lbal32[d].lib & complib32[d].lib\r
projects / ~shefty / rdma-win.git / commitdiff