Changes between Version 3 and Version 4 of BuildingTapWindows


Ignore:
Timestamp:
08/23/13 09:18:31 (6 years ago)
Author:
Samuli Seppänen
Comment:

Updated tap-windows build documentation

Legend:

Unmodified
Added
Removed
Modified
  • BuildingTapWindows

    v3 v4  
    1212
    1313{{{
     14$ cd /c/users/myuser
    1415$ git clone https://github.com/OpenVPN/tap-windows
    1516}}}
    1617
    17 Next you need to set some environment variables. For self-signed test certificates use something like this:
     18Now set some environment variables:
     19
     20{{{
     21set DDK=c:\WINDDK\7600.16385.1
     22set DEVCON32=c:\WINDDK\7600.16385.1\tools\devcon\i386\devcon.exe
     23set DEVCON64=c:\WINDDK\7600.16385.1\tools\devcon\amd64\devcon.exe
     24set DEVCON_BASENAME=devcon.exe
     25set SIGNTOOL=c:\WINDDK\7600.16385.1\bin\x86\signtool.exe
     26set MAKENSIS=C:\Program Files (x86)\NSIS
     27set OUTDIR=c:\users\myuser\tap-windows
     28}}}
     29
     30Some of these variables have sane default values, and you many not need to define all of them. If you use self-signed test certificates you also need these variables:
    1831
    1932{{{
     
    3548If 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.
    3649
     50To simplify variable setting in the future, you can create a batch file with all the above commands and run it before running ''configure.bat''.
     51
    3752= Building TAP-windows =
    3853
    39 First you need to configure the tap-windows build to use these using a Visual Studio command prompt:
     54First you need to configure the tap-windows build to use the variables you defined. Do this from a Visual Studio command prompt:
    4055
    4156{{{
     
    4358}}}
    4459
    45 This copies the variables to ''tap-windows\config-env.bat'', which is included during build. All that's left is to build the tap-windows drivers:
     60This copies the variables to ''tap-windows\config-env.bat'' and various other places. All that's left is to build the tap-windows drivers:
    4661
    4762{{{
     
    4964}}}
    5065
    51 Further customization for MSVC can be done using ''config-local.m4'' file which overrides variables or with environment variables which override auto detection code. This can be used, for example, to specify a custom DDK location. For details, see
     66If 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''.
     67
     68For details on available environment variables see
    5269
    5370{{{