The MS Windows version of Cava Packager has the command line processor from Inno Setup bundled with the installation. The Installer Project node provides access to basic Installer configuration.
If you build an installer, it will be available in the 'installer' subdirectory of your project directory. An Inno Setup script based on your installer choices will always be available in the installer directory regardless of whether you actually build an installer.
- Use Installer - Make Builds Installer Capable
- On Windows, Cava Packager makes a few additions to your release bundle if you are using the Inno Setup installer. These items are removed after installation. You need to make the build installer capable if you wish to use the installer. Note that you may not wish to use the self extracting zip or archives of your release folder if your builds are installer capable. The release folder and archives will contain the additional installer components that will not be removed when the archive is extracted. Whilst this won't affect your application funtionally, it may confuse users who may run the additional executables or scripts.
- Auto Create Installer
- If your build is installer capable, you may check this to always build an installer with your project builds. Alternatively provided your build is installer capable you can build an installer using the Distribution Menu or Toolbar.
- Pre Installer Script
- You may specify a Perl script here to be run before the Inno Setup installer is built. The Perl script will be run using the same Perl used to build the project. The script will receive two arguments:
- The path to the project release directory.
- The path to the project installer directory.
- One possible use of this script would be to parse and alter the innosetup.iss script file before Inno Setup builds the setup executable. Please note that if you create an installer from the toolbar or Distribution Menu, then you must account for the results of any previous running of your script against the release and installer directories. The installer and release directories are only cleaned when you run a full project build.
- A very simple example script
pre_installer.pl that adds a user password to the innosetup script is included in the examples folder of Cava Packager under installer.
- Installer Type
- The only available type with this edition of Cava Packager is Inno Setup
- Installer Base Name
- Enter the base name for your installer executable. You can then use the installer name options to configure the suffix of opertaing system, architecture and version information. The final name is displayed in the Installer Final Name field.
- Top Level Folder
- You can specify the top level folder for your installation here. When using the Inno Setup Installer you are no longer limited to using the root folder of the release tree as the top level folder name.
- Allow user to change install path.
- Set whether the end user can alter the installation path.
- Require administrator privileges to install.
- You may wish to set this if you always want to install to a specific location in %program files%. If the user cannot change location then they will always need admin privileges. Perhaps a better strategy is to leave this option unchecked and allow user to change install path. If the user wants to install to Program Files, then they can start the installer with admin privileges.
- Run post_install_script.pl
- You may optionally include a script named 'post_install_script.pl' within your application package. If this option is selected, the final part of the installation process will be to call 'do post_install_script.pl'. You can carry out whatever tasks you may wish in this scripts. Any errors will be ignored unless you specifically call 'exit' with a none zerto value. You may choose to check this option even if you do not provide a post_install_script.pl. If you have compressed a large number of resources, the first run of any of your executables may be slower than usual. The executable wrapper around the post install script will cause all of your compressed files to be extracted at installation time.
- Program Group
- Enter the name of the Program Group under which you wish to install your menu shortcuts.
- Edit Icon Items
- You can add, remove and edit shortcut items using the list buttons in the shortcut list.
- Bin folder Item
- Enter the name of an item that will be packaged in your bin folder. This does not have to be an executable. You may also enter documents. If you do enter a document name, it must be capable of being opened via ShellExecute so common document formats such as pdf, txt, html etc should work.
- Item Name
- The name that will be displayed for the shortcuts.
- Install Items
- Choose to create a menu shortcut, a desktop shortcut, or both.
- Command Line Params
- You can enter command line parameters that you wish to be passed to an executable when started via the shortcuts.
- Alternate Icon
- Normally, the shortcut will display the icon present in an executable or a default icon for documents or if no icon is in your file. You can specify a separate icon file to be displayed here. Once selected the file is added to your stored icon resources. If you alter or edit the original source file you will have to import the new version into your icon resources and select it.
Cava Packager Copyright © 2006-2012 Mark Dootson