Technical data

5. Creating the fli4l Archives/Boot media
5.2. Creating the fli4l Archives/Boot media under Windows
Utilize the tool ‘AutoIt3’ (http://www.autoitscript.com/site/autoit/). This enables a ‘graph-
ical’ edition, as well as dialogues which allow to change the variables described in the following
sections.
mkfli4l.bat
The Build program automatically recognizes the different boot types (Page 24).
The ‘mkfli4l.bat’ can be invoked directly from Windows Explorer, if you need no optional
parameters.
The actions of the Build program are controlled by different mechanisms:
• Configuration variable BOOT_TYPE from the config /base.txt
• Configuration file config /mkfli4l.txt
• Parameter of the build program
• Interactive settings in the GUI
The variable BOOT_TYPE (Page 24) decides which action the Build program executes:
• Create a bootable fli4l CD-ISO-Image
• Making the fli4l files available, for remote update
• Generating the fli4l files and direct remote update via SCP
• Hard drive pre-install of a suitably formatted CF in the Cardreader
• a.s.o.
The description of the variables in the configuration file config /mkfli4l.txt can be
found in Chapter Control file mkfli4l.txt (Page 259).
5.2.1. Command line options
The last control mechanism is appending of option parameters to the call of the Build program
on the command line. The control options correspond to those in the control file mkfli4l.txt.
Option parameters override the values from the control file. Out of convenience, the names of
the option parameters differ from the names of the variables from the control file. There is a
long and, to some extent, a short form:
Usage: mkfli4l.bat [options] [config-dir]
-c, --clean cleanup the build-directory
-b, --build <dir> sets build-directory to <dir> for the fli4l-files
-v, --verbose verbose - some debug-output
--filesonly creates only fli4l-files - does not create a disk
--no-squeeze don't compress shell scripts
-h, --help display this usage
254