Changes between Version 4 and Version 5 of BuildingTapWindows

Timestamp:

08/23/13 09:19:02 (11 years ago)

Author:

Samuli Seppänen

Comment:

--

BuildingTapWindows

@@ -48 +48 @@
 If you imported the kernel-mode code-signing certicate using Internet Explorer, you can use ''certmgr.exe'' to export it in PFX (=PKCS12) format. Just make sure to include the private key in the file and to give it a sufficiently strong password, which you then define using ''CODESIGN_PASS'' variable. The CA cross certificate can be obtained from your CA and most likely needs no modifications. The URL for the timestamping service is CA-specific, but trivial to locate.
 
-To simplify variable setting in the future, you can create a batch file with all the above commands and run it before running ''configure.bat''.
+To simplify variable setting in the future, you can create a batch file with all the above commands and run it before running ''configure.bat''. For details on available environment variables see
+
+{{{
+> configure --help
+}}}
+
 
 = Building TAP-windows =
@@ -66 +71 @@
 If you want to customize the build further, e.g. to build a custom TAP-Windows driver that can coexist with stock OpenVPN TAP-Windows driver, you can edit the ''version.m4'' or create a separate ''config-local.m4''. Any variables in ''config-local.m4'' should override those in ''version.m4''.
 
-For details on available environment variables see
-
-{{{
-> configure --help
-}}}
-
 Finally, if you're generating an OpenVPN installer with the your modified TAP-Windows driver, put the TAP-Windows installer on a webserver and point the [wiki:BuildingUsingGenericBuildsystem OpenVPN cross-compile buildsystem] to it.