Difference between revisions of "Making custom installation package"
| Line 1: | Line 1: | ||
'''''Making custom installation package''''' | '''''Making custom installation package''''' | ||
You need to run standard | You need to run standard installation package from command line (or batch-file) with your preferred file name *.iss as parameter, for example: | ||
[[File:AllMixInst_1.jpg]] | [[File:AllMixInst_1.jpg]] | ||
| Line 11: | Line 11: | ||
[[File:AllMixInst_3.jpg]] | [[File:AllMixInst_3.jpg]] | ||
You have to select new name and other parameters, like pictures for Logo, Splash, Icons. Custom built-in demo project is also available to change. | You have to select new name of application and other parameters, like pictures for Logo, Splash, Icons. Custom built-in demo project is also available to change. | ||
Next time you can use generated .iss file for automated build of new installation packages. | Next time you can use generated .iss file for automated build of new installation packages. | ||
Note: configuration file *.iss use absolute path, it means you need to edit it manually in case of migration to other place or repeat all from scratch. | |||
Latest revision as of 09:04, 23 November 2021
Making custom installation package
You need to run standard installation package from command line (or batch-file) with your preferred file name *.iss as parameter, for example:
First time, when *.iss file is not exist, such file: *.iss will be created and then configuration wizard will be runned and will ask you set of questions about generated package:
You have to select new name of application and other parameters, like pictures for Logo, Splash, Icons. Custom built-in demo project is also available to change. Next time you can use generated .iss file for automated build of new installation packages. Note: configuration file *.iss use absolute path, it means you need to edit it manually in case of migration to other place or repeat all from scratch.