@@ -77,7 +77,7 @@ with DSA private key, using SHA1 digest.
77
77
WinSparkle provides tools to generate keys and sign the update using OpenSSL.
78
78
79
79
You need ` openssl.exe ` available on Windows to use those tools (available as
80
- [ precompiled binary] [ OpenSSL binaries ] ).
80
+ [ precompiled binary] ( https://wiki.openssl.org/index.php/Binaries ) ).
81
81
82
82
Alternatively, you can generate keys and sign your updates even on macOS or Linux,
83
83
using [ tools provided by Sparkle project] ( https://github.com/sparkle-project/Sparkle/tree/master/bin ) .
@@ -108,25 +108,3 @@ to your appcast file:
108
108
109
109
Download the sources archive and have a look at the
110
110
[ examples/] ( https://github.com/vslavik/winsparkle/tree/master/examples ) folder.
111
-
112
-
113
- Using latest development versions
114
- -----------------------------------
115
-
116
- If you want to stay at the bleeding edge and use the latest, not yet released,
117
- version of WinSparkle, you can get its sources from public repository.
118
- WinSparkle uses git and and the sources are hosted on GitHub at
119
- https://github.com/vslavik/winsparkle
120
-
121
- WinSparkle uses submodules for some dependencies, so you have to initialize
122
- them after checking the tree out:
123
-
124
- $ git clone https://github.com/vslavik/winsparkle.git
125
- $ cd winsparkle
126
- $ git submodule init
127
- $ git submodule update
128
-
129
- Then compile WinSparkle as described above; no extra steps are required.
130
-
131
- [ OpenSSL source ] : https://www.openssl.org/source/
132
- [ OpenSSL binaries ] : https://wiki.openssl.org/index.php/Binaries
0 commit comments