ZBasic Language Reference
119
ZX Microcontroller Family
--target-device=<target>
This option specifies the target for which code should be generated. At present, the supported targets
are:
ZX24
ZX24a
ZX24p
ZX24n
ZX40
ZX40a
ZX40p
ZX40n
ZX44
ZX44a
ZX44p
ZX44n
ZX1281
ZX1281n
ZX1280
ZX1280n
ZX328n
ZX328l
ZX28n
ZX28l
ZX24e
ZX24ae
ZX24pe
ZX24ne
ZX128e
ZX128ne
ZX1281e
ZX1281ne
ZX328nu
If this option is used, it must appear before any modules are compiled. The default target is ZX24. The
target device may alternately be specified in the first module compiled using the Option
TargetDevice directive. Doing so will override the specification on the command line.
--temp-dir=<directory>
For native mode devices, the compiler generates several intermediate files in the process of compiling an
application. Normally, those files are created in a temporary subdirectory of the directory containing the
project file and then the directory and its content is deleted when the compilation is completed. The name
of the temporary directory is selected to avoid conflicting with any existing files and directories. If the
temporary files need to be examined, the -keep-files options can be used to prevent them from
being deleted in which case the directory in which they will be created will be zxTempDir. A separate
subirectory will be created in this temporary directory for each project compiled. If the default name of the
temporary directory is unsuitable, you may specify a different directory using the -temp-dir option. If
the specified directory is relative, it is interpreted as being relative to the directory containing the project
file.
--verbose
This option, useful only for native mode devices, causes the output from the final build process to be sent
to stderr. In the absence of this option, the output from the build process is captured in a file named
build.log created in the temporary directory. (Use the -keep-files option to prevent the build log
from being deleted after the build is complete.)
--version
This option causes the version number of the compiler to be sent to stdout. The compiler will then exit.
--warn=<warning-type>[,<warning-type>...]
This option enables or disables specific types of warnings. The warning types are described in the table
below. To disable a warning type, add the prefix no- to the warning type, e.g. no-unused-param. All
warnings may be disabled en masse using -warn=no-warnings.
Warning Type
Number Description
array-bounds
9
Warn about constant indices on arrays being outside of the valid range.
calltask-byref
1
Warn about invoking a task that uses ByRef parameters.
case-overlap
10
Warn about the same value appearing in more than one case
expression or range in a Select Case statement.
data-range
3
Warn about data values exceeding the capacity for the specified type.
for-loop-termination
11
Warn about a For loop that may not terminate properly.