From 5257749f01045ad643ddfa87ba7594231a346e2f Mon Sep 17 00:00:00 2001 From: stansmith Date: Thu, 17 Jul 2008 01:03:01 +0000 Subject: [PATCH] [WinOF] updated to discuss WDK build and WinOF/makebin/buildrelease structures git-svn-id: svn://openib.tc.cornell.edu/gen1@1402 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86 --- branches/WinOF/WIX/README.txt | 74 +++++++++++++++++++++++++---------- 1 file changed, 53 insertions(+), 21 deletions(-) diff --git a/branches/WinOF/WIX/README.txt b/branches/WinOF/WIX/README.txt index bb76b554..6deadcda 100644 --- a/branches/WinOF/WIX/README.txt +++ b/branches/WinOF/WIX/README.txt @@ -1,12 +1,5 @@ [5-28-08] -WinOF Revisions: - 1.0 based on svn.614 - 1.0.1 svn.864 - 1.1 svn.1177 - 2.0 svn.xxxx - - How to generate a Windows OpenFabrics Release (WinOF) using the WIX 2.0 open source installer tool set ( http://sourceforge.net/projects/wix/ ). @@ -17,22 +10,32 @@ WIX References: WIX Introduction http://wix.sourceforge.net/manual-wix2/wix_index.htm +WinOF Revisions: + 1.0 based on svn.614 + 1.0.1 svn.864 + 1.1 svn.1177 + 2.0 svn.xxxx + + + Creating a binary release tree ------------------------------ -As of WinFO 1.1 release [5-23-08] the build environment has been switched over to +As of WinOF 2.0 release [Aug'08] the build environment has been switched over to Microsoft WDK (Windows Driver Kit) version 6001.180001. -See gen1\trunk\BuildRelease.bat file to generate a Wix installer (.msi file). -The OS flavor (WLH, WXP or WNET - Vista/Server 2008[LongHorn], Server 2003+XP64 -and XP(x86)]) bin folders will be populated with the correct folder structure such that +See gen1\trunk\BuildRelease.bat file to generate a Wix installer (.msi file) containing +signed driver files. +The OS flavor WLH\ - Vista/Server 2008[LongHorn], WNET\ - Server 2003+XP64 +and XP\ (x86 only) bin folders will be populated with the correct folder structure such that a WIX installer (.msi) files can be generated; either cd into OS\arch dir and -run nmake or use BuildRelease.bat from trunk\ folder. +run buildmsi.bat or use BuildRelease.bat from trunk\ folder. -Warning - buildrelease.bat is not generic, some asembly required. -BuildRelease.bat will by default deposit 7 .msi files in -'%SystemRoot%\temp\WinOF_OS_xxx.msi'; OS flavor_arch is the convention. +Warning - buildrelease.bat is not generic, some asembly required as the folder +structure is assumed. +BuildRelease.bat will by default deposit 7 .msi files in +'%SystemRoot%\temp\WinOF_OS_arch.msi'. The other approach to creating a binary release tree is to generate the @@ -45,10 +48,22 @@ contents of WIX\bin\ yourself from a WDK/SDK build window which can run 2) cd trunk\etc; execute 'makebin src-dir dest-dir OS-flavor' for each OS flavor: wnet, wlh and wxp. - Say your svn repository is at C:\open-ib\, then to generate a binary - release from a command window: - makebin C:\open-ib\gen1\trunk C:\open-ib\gen1\branches\WinOF\Wix\bin - + Say your svn repository is at C:\open-ib\, then to populate the WIX bin + folder for Server 2008 binaries from a command window: + makebin C:\open-ib\gen1\trunk C:\open-ib\gen1\branches\WinOF\Wix\WLH\bin WLH + +With the arrival of Windows Server 2008 & Vista (WLH - Windows LongHorn) driver signing +is a requirement. The WIX\sign-all-drivers.bat script will create a .cat file for each +driver .inf located. The generation of the .cat file is driven from the corresponding +.cdf file (.inf + .cdf + all files listed in .cdf + inf2cat.exe & signtool.exe result +in a .cat file). + +A SW publisher's digital-ID certificate is required in order for WinOF installers to +be created. A test certificate can be generated for local use, requires overhead during +installation (reboot & local certificate store updates). The MS prescribed procedure is +to obtain a SW publisher's certificate from VeriSign or other agency; if your company +is producing SW drivers for SVR2008, then you will likely have access to a cert file. +The OFA will be purchasing a certificate for WinOF publication. Creating a WIX tool set ------------------------- @@ -87,13 +102,28 @@ Update the trunk\doc\Manual.htm file for new features. BUILDING a .msi installer image file ------------------------------------ +Easy way: + place certificate file in WIX\ folder. + cd trunk\ + From a standard DOS cmd window, not a WDK cmd window, say + buildrelease clean + buildrelease all # .msi file created in %windir%\temp\*.msi + + buildrelease makebin - assumes trunk\bin\* built, populates WIX\{wlh,wnet,wxp}\bin folders. + buildrelease msi - signs & creates installers assuming makebin has been run. + buildrelease wix - just creates .msi installers - assumes all bin\ folders populated. + +CPU specific builds + CD to the WIX OS-flavor and architecture specific directory. 'nmake.exe' needs to be in your command window search path. Build three arch specific installers (.msi files) for WLH and WNET; WXP is x86 only. -WARNING - assupmtion is .\bin is populated correctly from makebin.bat or BuildRelease.bat. + +WARNING: + assupmtion: .\bin is populated correctly from makebin.bat or BuildRelease.bat makebin. cd gen1\branches\WinOF\WIX\wlh\x86 & nmake - Results in a WOF_wlh_x86.msi installer image. + Results in a .\WOF_wlh_x86.msi installer image. cd gen1\branches\WinOF\WIX\wlh\x64 & nmake Results in a WOF_wlh_x64.msi installer image. @@ -108,6 +138,8 @@ Create a log file for a given installation: msiexec /I "WOF_x86.msi" /Lv \temp\msi.log + Also see %windir%\inf\setupapi.dev.log on Svr08 & Vista for driver load logging. + Command line way to set an interface's IP address, netmask, no gateway: netsh interface ip set address "Local Area Connection 3" static 10.10.4.200 255.255.255.0 -- 2.41.0