Changes between Version 2 and Version 3 of BuildClientProcedure

Timestamp:

Jul 30, 2007, 10:06:04 AM (17 years ago)

Author:

romw

Comment:

checkpoint

BuildClientProcedure

@@ +1 @@
+[[PageOutline]]
 = Client Build Procedure =
 
@@ -7 +8 @@
 If this is a major or minor version change to an even numbered minor revision you'll need to fork the tree.
 
- 1. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN | Branch/Tag'
- 2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>`, where `<major>` is the major version number and `<minor>` is the minor version number.
- 3. Adjust version numbers in both the new branch and truck so that the new branch and trunk
+{{{
+1. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN\Branch/Tag'
+2. Change the "To URL:" to 'http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>'
+}}}
+
+Where <major> is the major version number and <minor> is the minor version number.
+
+{{{
+3. Adjust version numbers in both the new branch and truck so that the new branch and trunk
    reflect the current development efforts.
+}}}
 
-The branch should represent the new stable major and even minor version numbers. Trunk should represent the next major and odd minor version number.
+The branch should represent the new stable major and even minor version numbers. Trunk should represent the 
+next major and odd minor version number.
 
-The files that need to be modified are `configure.ac` and `version.h`.
+The files that need to be modified are configure.ac and version.h.
 
 Example: Branch 5.10.x and Trunk 5.11.0.
@@ -24 +33 @@
 Increment the revision number in the files dealing with version numbers.
 
-The files that need to be modified are `configure.ac` and version.h`.
+The files that need to be modified are configure.ac and version.h.
 
 Commit all changes to SVN.
 
- 1. Right-click on the branch directory, and then select 'TortoiseSVN\Branch/Tag'
- 2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>`
+{{{
+1. Right-click on the branch directory, and then select 'TortoiseSVN\Branch/Tag'
+2. Change the "To URL:" to 'http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>'
+}}}
 
 Where <major> is the major version number, <minor> is the minor version number, and <revision> is the revision number.
+
+== Build Client ==
+
+Launch the boinc.sln project file and build both the x86 and x64 targets.
+
+== Sanity Test New Binaries ==
+
+Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 mins. Traverse 
+all the tabs, verify the status fields as a result traverses the crunching process.
+
+== Code Sign Binaries ==
+
+The the SignCode.cmd file from the win_build directory. This batch file should be run from within a Visual
+Studio command shell. SignCode should contain a series of the following line:
+
+{{{
+
+signtool sign /f "boinc.pfx" /p "<password>" /d "BOINC Client Software" /du "http://boinc.berkeley.edu" 
+/t "http://timestamp.verisign.com/scripts/timstamp.dll" /sha1 "2F0BDC8DD84A56417C68B53B29DD12155760652D" 
+.\Build\Win32\ReleaseSigned\boinc.dll
+
+}}}
+
+A call to signtool should be executed for each binary shipped in the setup package.
+
+Use [urlhttp://msdn2.microsoft.com/en-us/library/aa906332.aspx pvk2pfx] to convert the spc/pvk certificate pair into
+a pfx file.
+
+Replace '<password>' with the correct private key password used to create the private/public key pair.