-[6-15-07]\r
+[8-06-07]\r
\r
-How to generate a Windows OpenFabrics Release (WinOF) using the WIX 2.0 open source installer\r
-tool set ( http://sourceforge.net/projects/wix/ ).\r
+How to generate a Windows OpenFabrics Release (WinOF) using the WIX 2.0 open\r
+source installer tool set ( http://sourceforge.net/projects/wix/ ).\r
\r
WIX References:\r
WIX collection http://www.dalun.com/wix/default.htm\r
WIX sourceforge project http://sourceforge.net/projects/wix/\r
WIX Introduction http://wix.sourceforge.net/manual-wix2/wix_index.htm \r
\r
-Download the latest openib-windows binary release to 'bin\';\r
-(svn.614 was used for winOF 1.0).\r
\r
-The .zip archives reduce the download/copy overhead.\r
+Creating a binary release tree\r
+------------------------------\r
+\r
+Download the latest openib-windows binary release from \r
+http://openib.tc.cornell.edu/downloads/binaries/ to 'branches\WinOF\Wix\bin\'\r
+(svn.614 was used for winOF 1.0).\r
+The downloaded .zip archives reduce the download/copy overhead.\r
\r
-The resulting bin\ folder structure must be structured like the following:\r
+The resulting WIX\bin\ folder must be structured like the following:\r
\r
- bin\\r
+ WIX\bin\\r
DAPL\\r
amd64\\r
x86\\r
debug\\r
release\\r
\r
-Down load the WIX v2 (stable) tool set (http://sourceforge.net/projects/wix/) to \91WIX_tools\92.\r
-Unzip the archive to a folder within WIX_tools\ which represents the version of the tool set.\r
+\r
+The other approach to creating a binary release tree is to generate the\r
+contents of WIX\bin\ yourself from a DDK/SDK build window which can run\r
+'nmake'.\r
+\r
+ 1) Generate binaries for each supported architecture: x86, x64 and ia64.\r
+ cd to trunk; build -wcf from a DDK command window for the respective arch.\r
+\r
+ 2) cd trunk\etc; execute 'makebin src-dir dest-dir'\r
+ Say your svn repository is at C:\open-ib\, then to generate a binary\r
+ release from a command window:\r
+ makebin C:\open-ib\gen1\trunk C:\open-ib\gen1\branches\WinOF\Wix\bin\r
+ Answer 'F' to the few xcopy prompts.\r
+\r
+\r
+Creating a WIX tool set\r
+-------------------------\r
+\r
+Download the WIX v2 (stable) tool set (http://sourceforge.net/projects/wix/)\r
+to \91WIX_tools\\92.\r
+Unzip the archive to a folder within 'WIX_tools\' as this represents the\r
+version of the tool set.\r
Something like unzip wix-2.0.5325.0-binaries.zip into wix-2.0.5325.0-binaries\.\r
You would now have the following structure:\r
WIX\WIX_tools\wix-2.0.5325.0-binaries\{candle.exe, light.exe,...}\r
\r
\r
-RELEASE UPDATES:\r
-----------------\r
+\r
+Updating Relase Files\r
+---------------------\r
\r
Update Release_notes.htm file.\r
\r
\r
Know issues\r
\r
-Update the Manual.htm file for new features, etc.\r
+Update the trunk\doc\Manual.htm file for new features.\r
\r
\r
-BUILDING a .msi installer image\r
--------------------------------\r
+BUILDING a .msi installer image file\r
+------------------------------------\r
\r
-CD to an architecture specific directory.\r
-'nmake.exe' needs to be in your command window search path.\r
+CD to the WIX architecture specific directory. 'nmake.exe' needs to be\r
+in your command window search path. Build three arch specific installers\r
+(.msi files).\r
\r
-x86> nmake\r
- \r
+gen1\branches\WinOF\WIX\x86> nmake\r
Results in a WOF_x86.msi installer image.\r
\r
+gen1\branches\WinOF\WIX\x64> nmake\r
+ Results in a WOF_x64.msi installer image.\r
+\r
+gen1\branches\WinOF\WIX\ia64> nmake\r
+ Results in a WOF_ia64.msi installer image.\r
+\r
\r
DEBUG\r
-----\r