chylex/TweetDuck
1
0
Fork 0
mirror of https://github.com/chylex/TweetDuck.git synced 2025-04-23 21:15:49 +02:00
Code

Revert README change & lock Inno Setup to version 5.6.1

Browse Source
This commit is contained in:
Daniel Chýlek 2019-07-13 19:39:08 +02:00 committed by GitHub
parent f7359ebc8a
commit 42a5e72f19
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 8 deletions

10
README.md
View File

@ -44,15 +44,9 @@ If you decide to publicly release a custom version, please make it clear that it
### Installers
TweetDuck uses **Inno Setup** for installers and updates. First, download and install [InnoSetup QuickStart Pack](http://www.jrsoftware.org/isdl.php) (non-unicode; editor and encryption support not required) and the [Inno Download Plugin](https://code.google.com/archive/p/inno-download-plugin).
TweetDuck uses **Inno Setup** for installers and updates. First, download and install [InnoSetup 5.6.1](http://files.jrsoftware.org/is/5/innosetup-5.6.1.exe) (with Preprocessor support) and the [Inno Download Plugin 1.5.0](https://drive.google.com/folderview?id=0Bzw1xBVt0mokSXZrUEFIanV4azA&usp=sharing#list).
Next, add the Inno Setup installation folder (usually `C:\Program Files (x86)\Inno Setup 6`) into your **PATH** environment variable. You may need to restart File Explorer for the change to take place.
For Inno Setup 6, the Inno Download Plugin fails to automatically include itself in the installation scripts. To fix that, open `ISPPBuiltins.iss` in the Inno Setup 6 installation folder, and add the following line at the end:
```
#pragma include __INCLUDE__ + ";" + ReadReg(HKLM, "Software\Mitrich Software\Inno Download Plugin", "InstallDir")
```
Next, add the Inno Setup installation folder (usually `C:\Program Files (x86)\Inno Setup 5`) into your **PATH** environment variable. You may need to restart File Explorer and Visual Studio for the change to take place.
Now you can generate installers by running `bld/GEN INSTALLERS.bat`. Note that this will only package the files, you still need to run the [release build](#release) in Visual Studio first!