aboutsummaryrefslogtreecommitdiffstats
path: root/msi-example/README.md
diff options
context:
space:
mode:
authorSimon Rozman <simon@rozman.si>2020-10-25 00:23:33 +0200
committerSimon Rozman <simon@rozman.si>2020-10-31 06:55:58 +0100
commit202f1dc9b88e2d962573e694a9abf38472575f9d (patch)
treeeab98197015c2760df25f5aa698383530c060d6f /msi-example/README.md
parentapi: allow wintun.h use in C++ (diff)
downloadwintun-202f1dc9b88e2d962573e694a9abf38472575f9d.tar.xz
wintun-202f1dc9b88e2d962573e694a9abf38472575f9d.zip
api: update README.md
Signed-off-by: Simon Rozman <simon@rozman.si>
Diffstat (limited to 'msi-example/README.md')
-rw-r--r--msi-example/README.md46
1 files changed, 0 insertions, 46 deletions
diff --git a/msi-example/README.md b/msi-example/README.md
deleted file mode 100644
index 0a42201..0000000
--- a/msi-example/README.md
+++ /dev/null
@@ -1,46 +0,0 @@
-## Example Standalone MSI
-
-The best way to include Wintun in your software is by including the MSMs in your final MSI,
-as described by [the main README](../README.md). However, if you're stuck with an installation
-system such as NSIS, which can not bundle MSM files, then you must build your own MSI, which
-NSIS can then invoke. ***Do not use an MSI from elsewhere. You must build it yourself and
-distribute only the MSI that you yourself build.*** Otherwise different projects will wind up
-uninstalling each other by accident and disturbing the MSM reference counting. The steps in
-this file should only be taken if you're not able to include an MSM into a MSI, something that
-is easily possible using WiX or most commercial installation solutions.
-
-This `msi-example` folder contains a WiX skeleton and a build script that handles all
-dependencies. use it as follows below.
-
-#### Steps:
-
-1. Generate a UUID using uuidgen.exe and replace `{{{FIXED AMD64 UUID}}}` in exampletun.wxs
-with that UUID. For the life time of your entire product, even across versions, do not change
-that UUID.
-
-2. Generate a UUID using uuidgen.exe and replace `{{{FIXED ARM64 UUID}}}` in exampletun.wxs
-with that UUID. For the life time of your entire product, even across versions, do not change
-that UUID.
-
-3. Generate another UUID using uuidgen.exe and replace `{{{FIXED X86 UUID}}}` in
-exampletun.wxs with that UUID. For the life time of your entire product, even across versions,
-do not change that UUID.
-
-4. Go to [Wintun.net](https://www.wintun.net/) and look at what the latest version is (`0.6`,
-for example). Replace `{{{VERSION}}}` in build.bat with that version.
-
-5. Download the amd64 MSM from [Wintun.net](https://www.wintun.net/) and compute its SHA2-256
-sum in all lowercase hex digits using `CertUtil -hashfile "path/to/file" SHA256`, and replace
-`{{{64BIT HASH}}}` in build.bat with that value.
-
-6. Download the arm64 MSM from [Wintun.net](https://www.wintun.net/) and compute its SHA2-256
-sum in all lowercase hex digits using `CertUtil -hashfile "path/to/file" SHA256`, and replace
-`{{{64BIT HASH}}}` in build.bat with that value.
-
-7. Download the x86 MSM from [Wintun.net](https://www.wintun.net/) and compute its SHA2-256
-sum in all lowercase hex digits using `CertUtil -hashfile "path/to/file" SHA256`, and replace
-`{{{32BIT HASH}}}` in build.bat with that value.
-
-8. Run build.bat.
-
-9. Distribute dist\exampletun-*.msi for your own software only.