Here is the tricky part in order to build our package we need to use MsBuild with a number of parameters and environmental variables as they are defined by the Delphi installation. This simple structure makes Inno Setup scripts very easy to read and edit using any text editor, although using Inno Setup. The Inno Setup Example Scripts are located in a separate folder.
![inno script studio defaultdirname inno script studio defaultdirname](http://m-and-i.cocolog-nifty.com/photos/uncategorized/2017/07/19/3.jpg)
Build of the package for different platforms Entries in an Inno Setup script file are organized into sections much like an INI file: section headers are enclosed in square brackets and each section header is followed by one or more section entries, one entry per line. DefaultDirName: DefaultGroupName: DefaultUserInfoName: DefaultUserInfoOrg: DefaultUserInfoSerial. We, first, check whether there is an appropriate Delphi installation before we proceed and, then, we delete any old BPL files.
![inno script studio defaultdirname inno script studio defaultdirname](https://i.ytimg.com/vi/gpufb8seut4/maxresdefault.jpg)
![inno script studio defaultdirname inno script studio defaultdirname](http://www.yx12345.com/fujians/2020/0224/20200224091206212.jpg)
Personally, I use the following structure as I find easy to keep track of in a version control system. define MyAppProjectFileDesc OpenShot Project File 18 define MyAppPublisher OpenShot Studios.
#INNO SCRIPT STUDIO DEFAULTDIRNAME CODE#
5.2 Build of the package for different platformsīefore we start delving into the installation script, we need to do some planning regarding where the source code of the packages will sit and where we will store the compiled units. 1 Script generated by the Inno Setup Script Wizard.4 Getting Ready for the Package Installation.