![]() For multi-platform CDROM installers, the preBuildActionList is executed once at the beginning of the CDROM build, and then again for every one of the specific platform installers.Įxecutes after generating the installer file. These actions usually include setting environment variables or performing some kind of processing on the files that will go into the installer before they are packed into it. Action lists include your actions of choice and are executed at a specific point of the installation process as outlined below.īitRock InstallBuilder Action Lists (in order of execution)Įxecutes before generating the installer file. You can place your action lists in the main installer project or in one of its components. It is important to understand how and when each action must be performed, what differences exist between action lists inside components and within the primary installer, how the installer will behave when you run it in different installation modes (GUI, text, or unattended) and what happens when you generate rpm or deb packages. InstallBuilder actions are organized in what are called action lists, which are executed at specific points of the installation process. ![]() Actions can be accessed by editing the XML project file directly or in the 'Advanced' section of the InstallBuilder GUI. BitRock InstallBuilder includes a number of useful built-in actions to facilitate adding complex functionality to your installer. You may need to check a registry value, create a configuration file, execute a particular command, make substitutions in text files or even connect to an external server via a HTTP POST request. ![]() This is especially the case for more sophisticated configurations, such as when you need to execute different platform-specific actions at different stages of the installation process. Creating an installer is not as straightforward as most people think.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |