Difference between revisions of "Making custom installation package"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
'''''Making custom installation package''''' | '''''Making custom installation package''''' | ||
You need to | You need to run standard AllMix installation package from comand line (or batch-file) with file name *.iss as parameter, for example: | ||
[[File:AllMixInst_1.jpg]] | [[File:AllMixInst_1.jpg]] | ||
First time, when .iss file is | 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: | ||
[[File:AllMixInst_2.jpg]] | [[File:AllMixInst_2.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. | 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. | ||
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. | ||
Revision as of 08:55, 23 November 2021
Making custom installation package
You need to run standard AllMix installation package from comand line (or batch-file) with 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 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.