Setup kit: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
The first time Axel releases to the customer a setup-kit archive that contains LogicLab binaries and all other files needed (script, catalog files, setup files, common dll, standard images and icons) that you need to make your own setup and to start to customize it. | The first time Axel releases to the customer a setup-kit archive that contains LogicLab binaries and all other files needed (script, catalog files, setup files, common dll, standard images and icons) that you need to make your own setup and to start to customize it. | ||
# Download your setup-kit archive available on your Quixplorer page at [http://www.axelsw.it/Expl/] | # Download your setup-kit archive available on your Quixplorer page at [http://www.axelsw.it/Expl/] | ||
# Extract the archive file in your working directory | # Extract the archive file in your working directory es: ''L:\Test\MyCatalog\ | ||
# Apply the customizations you need including : | # Apply the customizations you need including : | ||
#* Custom graphical appearance, featuring custom icon, splash screen, and welcome page. See '''LLMakeCustomVersions.bat''' | #* Custom graphical appearance, featuring custom icon, splash screen, and welcome page. See '''LLMakeCustomVersions.bat''' | ||
| Line 18: | Line 18: | ||
#* arbitrarily complex wizards, for meta-programming or to support to your products (for example, firmware upgrade, automatic generation of text/binary files so on) | #* arbitrarily complex wizards, for meta-programming or to support to your products (for example, firmware upgrade, automatic generation of text/binary files so on) | ||
#* Additional documentations | #* Additional documentations | ||
# Run the Inno Setup compiler script | # Run the Inno Setup compiler script ''L:\Test\MyCatalog\Setup\LogicLab.iss'' | ||
# Your setup file is created into ''L:\Test\MyCatalog\Setup\Output'' folder and ready to be distributed | # Your setup file is created into ''L:\Test\MyCatalog\Setup\Output'' folder and ready to be distributed | ||
Revision as of 11:42, 13 January 2015
The LogicLab setup-kit allows the customer to create and distribute a custom version of the LogicLab IDE, additional components and catalog.
To create your custom setup-kit follow this procedure:
REQUIREMENT
- The login and password assigned by Axel for your customer page at [1]
- Inno Setup compiler available at [2]
CREATE YOU FIRST SETUP-KIT
The first time Axel releases to the customer a setup-kit archive that contains LogicLab binaries and all other files needed (script, catalog files, setup files, common dll, standard images and icons) that you need to make your own setup and to start to customize it.
- Download your setup-kit archive available on your Quixplorer page at [3]
- Extract the archive file in your working directory es: L:\Test\MyCatalog\
- Apply the customizations you need including :
- Custom graphical appearance, featuring custom icon, splash screen, and welcome page. See LLMakeCustomVersions.bat
- Libraries
- Sample projects
- arbitrarily complex wizards, for meta-programming or to support to your products (for example, firmware upgrade, automatic generation of text/binary files so on)
- Additional documentations
- Run the Inno Setup compiler script L:\Test\MyCatalog\Setup\LogicLab.iss
- Your setup file is created into L:\Test\MyCatalog\Setup\Output folder and ready to be distributed
UPDATE YOUR SETUP-KIT
LogicLab new releases are available on your customer's page. When you need to upgrade your setup-kit to include the new version of LogicLab follow this procedure. Only the LogicLab binaries will be updated, your customization won't be affected.
- Download LogicLab redistributable archive available on your customer page at [4]
- Copy it to your working directory L:\Test\MyCatalog and extract all files overwriting existing ones.
- If you need any further customizations on the catalog then perform them.
- Run the Inno Setup compiler script L:\Test\MyCatalog\Setup\LogicLab.iss
- Your setup file is created into L:\Test\MyCatalog\Setup\Output folder and ready to be distributed