Changes between Version 58 and Version 59 of Windows build instructions

Timestamp:

Jun 9, 2017 2:02:58 PM (7 years ago)

Author:

Frank Mehnert

Comment:

--

Windows build instructions

@@ -137 +137 @@
 === Only for 64 bit builds: setting up self signing ===
 
-Part 1: creating and installing the test certificate
+Setting up test signing will allow to build signed binaries to make Windows happy. To use the test-signed binaries, the target machine has to run in test signing mode and the test certificate has to be installed on the target machine.
+
+'''Part 1:''' creating and installing the test certificate
  1. Launch an elevated command line shell (Vista and later).
  1. {{{makecert.exe -r -pe -ss my -n "CN=MyTestCertificate" mytestcert.cer}}}
@@ -145 +147 @@
  1. Keep the mytestcert.cer file in a safe place.
 
-Part 2: configuring the system to run test signed code (Vista and later)
+'''Part 2:''' configuring the system to run test signed code (Vista and later)
  1. Launch an elevated command line shell (Vista and later).
  1. Run {{{Bcdedit.exe -set TESTSIGNING ON}}} on an elevated cmd.exe prompt.
@@ -153 +155 @@
  1. Vista: "Test Mode" will appear in all four corners of the desktop and "Microsoft (R) Windows (R) (Build 6000)" will appear on the top. Windows 7: "Test Mode<CR>Windows 7<CR>Build 7600" will appear in the lower right corner.
 
-Part 3: building !VirtualBox with signing enabled
+'''Part 3:''' building !VirtualBox with signing enabled
  1. If you called the certificate something other than !MyTestCertificate you'll have make the appropriate overrides in `LocalConfig.kmk`. See the `Code Signing` section of `Config.kmk` for what can be overridden.
  1. Add `VBOX_SIGNING_MODE=test` to `LocalConfig.kmk`.
@@ -170 +172 @@
 Before you can start any binary from the output directory you have to make sure that external libraries (for example `libcurl.dll` or `libcrypto.dll`) are located in a directory which is accessible by the `PATH` variable or by copying these libraries to the output directory.
 
-In order to (re-)install the !VirtualBox kernel drivers, issue the following:
+In order to (re-)install the !VirtualBox kernel drivers ('''drivers have to be signed'''), issue the following:
 {{{
 loadall.cmd