diff --git a/installers/windows/Monero.iss b/installers/windows/Monero.iss index cfe18f36..3a7660cb 100644 --- a/installers/windows/Monero.iss +++ b/installers/windows/Monero.iss @@ -1,4 +1,4 @@ -; Monero Boron Butterfly GUI Wallet Installer for Windows +; Monero Carbon Chamaeleon GUI Wallet Installer for Windows ; Copyright (c) 2017-2019, The Monero Project ; See LICENSE @@ -8,7 +8,7 @@ AppName=Monero GUI Wallet ; Thus it's important to keep this stable over releases ; With a different "AppName" InnoSetup would treat a mere update as a completely new application and thus mess up -AppVersion=0.14.1.2 +AppVersion=0.15.0.0 DefaultDirName={pf}\Monero GUI Wallet DefaultGroupName=Monero GUI Wallet UninstallDisplayIcon={app}\monero-wallet-gui.exe @@ -58,7 +58,7 @@ Name: "en"; MessagesFile: "compiler:Default.isl" ; .exe/.dll file possibly with version info). ; ; This is far more robust than relying on version info or on file dates (flag "comparetimestamp"). -; As of version 0.14.1.0, the Monero .exe files do not carry version info anyway in their .exe headers. +; As of version 0.15.0.0, the Monero .exe files do not carry version info anyway in their .exe headers. ; The only small drawback seems to be somewhat longer update times because each and every file is ; copied again, even if already present with correct file date and identical content. ; @@ -197,7 +197,7 @@ begin // Additional wizard page for entering a special blockchain location blockChainDefaultDir := ExpandConstant('{commonappdata}\bitmonero'); s := 'The default folder to store the Monero blockchain is ' + blockChainDefaultDir; - s := s + '. As this will need more than 70 GB of free space, you may want to use a folder on a different drive.'; + s := s + '. As this will need more than 74 GB of free space, you may want to use a folder on a different drive.'; s := s + ' If yes, specify that folder here.'; BlockChainDirPage := CreateInputDirPage(wpSelectDir, diff --git a/installers/windows/README.md b/installers/windows/README.md index 0b17a076..37424199 100644 --- a/installers/windows/README.md +++ b/installers/windows/README.md @@ -6,7 +6,7 @@ Copyright (c) 2017-2019, The Monero Project This is a *Inno Setup* script `Monero.iss` plus some related files that allows you to build a standalone Windows installer (.exe) for -the GUI wallet that comes with the Boron Butterfly release of Monero. +the GUI wallet that comes with the Carbon Chamaeleon release of Monero. This turns the GUI wallet into a more or less standard Windows program, by default installed into a subdirectory of `C:\Program Files`, a @@ -18,7 +18,7 @@ Monero. As the setup script in file [Monero.iss](Monero.iss) has to list many files and directories of the GUI wallet package to install by name, this version of the script only works with exactly the GUI wallet -for Monero release *Boron Butterfly* that you find on +for Monero release *Carbon Chamaeleon* that you find on [the official download page](https://getmonero.org/downloads/). It should however be easy to modify the script for future @@ -32,15 +32,15 @@ See [LICENSE](LICENSE). You can only build on Windows, and the result is always a Windows .exe file that can act as a standalone installer for the -Boron Butterfly GUI wallet. +Carbon Chamaeleon GUI wallet. Note that the installer build process is now reproducible / deterministic. For details check the file [Deterministic.md](Deterministic.md). The build steps in detail: 1. Install *Inno Setup*. You can get it from [here](http://www.jrsoftware.org/isdl.php) -2. Get the Inno Setup script plus related files by cloning the whole [monero-gui GitHub repository](https://github.com/monero-project/monero-gui); you will only need the files in the installer directory `installers\windows` however. Depending on development state, additionally you may have to checkout a specific branch, like `release-v0.14`. -3. The setup script is written to take the GUI wallet files from a subdirectory named `bin`; so create `installers\windows\bin`, get the zip file of the GUI wallet from [here](https://getmonero.org/downloads/), unpack it somewhere, and copy all the files and subdirectories in the single subdirectory there (currently named `monero-gui-0.14.1.2`) to this `bin` subdirectory +2. Get the Inno Setup script plus related files by cloning the whole [monero-gui GitHub repository](https://github.com/monero-project/monero-gui); you will only need the files in the installer directory `installers\windows` however. Depending on development state, additionally instead of simply using `master` you may have to checkout a specific branch, like `release-v0.15`. +3. The setup script is written to take the GUI wallet files from a subdirectory named `bin`; so create `installers\windows\bin`, get the zip file of the GUI wallet from [here](https://getmonero.org/downloads/), unpack it somewhere, and copy all the files and subdirectories in the single subdirectory there (currently named `monero-gui-0.15.0.0`) to this `bin` subdirectory 4. Start Inno Setup, load `Monero.iss` and compile it 5. The result i.e. the finished installer will be the file `mysetup.exe` in the `installers\windows\Output` subdirectory diff --git a/installers/windows/ReadMe.htm b/installers/windows/ReadMe.htm index aee7adf1..f9e044ea 100644 --- a/installers/windows/ReadMe.htm +++ b/installers/windows/ReadMe.htm @@ -1,13 +1,13 @@
-Copyright (c) 2014-2019, The Monero Project
- Date: July 20, 2019
You just installed the Monero GUI wallet for Windows, release Boron Butterfly, version 0.14.1.2. +
You just installed the Monero GUI wallet for Windows, release Carbon Chamaeleon, version 0.15.0.0. The wallet enables you to send and receive Moneroj in a secure and very private way.
@@ -61,7 +61,7 @@ provides the most security and privacy possible for you.However if your Internet access makes it difficult to run a full node, or if you have simply no room to store - the blockchain locally (somewhat over 70 GB in July 2019, and of course growing), you can compromise and try to connect + the blockchain locally (somewhat over 74 GB in November 2019, and of course growing), you can compromise and try to connect to a remote node. One way of finding such a node is checking this page.
diff --git a/installers/windows/WelcomeImage.bmp b/installers/windows/WelcomeImage.bmp index e286cf39..e6faffa6 100644 Binary files a/installers/windows/WelcomeImage.bmp and b/installers/windows/WelcomeImage.bmp differ