Inno Setup

First you need to download the sources from Github. From the command line do: To be able to contribute to Inno Setup, clone your own fork instead of cloning the main Inno Setup repository, commit your work on topic branches and make pull requests. See [CONTRIBUTING.md]. We compile all of Inno Setup's projects under Delphi 12.3 Athens with the May Patch installed. There's a free version of Delphi available called the Community Edition. See After installation of Delphi, you must install GetIt dependencies by running getit.bat and following the instructions. Install Microsoft HTML Help Workshop if you haven't already done so. See and Note: Microsoft HTML Help Workshop is only needed to be able to compile the help file. Unfortunately, Embarcadero has removed command line compilation support from the Community Edition, which means there's two different build scripts. Community Edition: To build all files in Release mode run build-ce.bat and follow the instructions. Otherwise: To build all files in Release mode run build.bat and follow the instructions. To just compile 64-bit Inno Setup in Release mode run compile.bat x64 and follow the instructions. Run compile.bat x86 for 32-bit Inno Setup. To compile just one project, append its project name, for example compile.bat x64 ISCC . These batch files cannot be used with the Community Edition, open Projects Projects.groupproj instead. To just compile the Inno Setup help file and its web version run compile.bat x64 ISHelpGen and ISHelp compile.bat and follow the instructions. The former batch file cannot be used with the Community Edition, open Projects Projects.groupproj instead. Component Installation If you intend to view or modify the Setup project's forms, you must install the following component units, which can be found in the [Components] directory. BitmapButton BitmapImage FolderTreeView NewCheckListBox NewCtrls NewNotebookReg NewProgressBar NewStaticText PasswordEdit RichEditViewer If you intend to view or modify the ISIDE project's forms, you must additionally install the following components. DropListBox NewGroupBox NewTabSet The [Components] directory contains a Components.dpk file which you can use to install all these components. If you only want to edit code, then you may skip installation of the components, and choose "Cancel" if the Delphi IDE tells you a class can't be found. The [Components] directory also includes various units that are not installable components; however, they are still considered components because they can function independently from Inno Setup. ISIDE - This is the GUI front-end for the compiler, also known as the Compiler IDE. ISIDE does not do the actual compilation itself; it relegates it to ISCmplr.dll. If the ISCmplr project is changed, you normally don't need to recompile ISIDE since it's essentially a text editor, and is not affected by internal changes to the compiler. Setup - This is the actual "Setup" program. It displays the wizard, and performs all (un)installation-related tasks. SetupLdr - This is the "setup loader." It self-extracts a compressed Setup program into the user's TEMP directory and runs it from there. It also displays the "This will install..." and /HELP message boxes. ISSigTool - This is a command-line utility which can be used to sign and verify any of your files. ISIDE, ISCC, and ISCmplr use these signatures to verify the authenticity of a number of DLL, E32, E64, and EXE files before loading them. Note: this utility does not replace Microsoft's signtool.exe in any way and is in fact not related to Authenticode Code Signing at all. ISTestTool - This is an internal command-line utility which runs unit tests. It is run automatically by build.bat and build-ce.bat after compilation, and exits with a non-zero exit code as soon as a test fails. Does not use a testing framework. Run test.bat to compile and run the tests manually. Source code tips When building the projects in Release mode, it outputs to