Page 162 of 229 Start Back Next End ZBasic Language Reference 152 ZBasic Microcontrollers which –-device-parameter options are not allowed) but will be processed when compiling for a generic target device (for which –-device-parameter options must be specified). The second form is useful when you want to specify the target device in the configuration file as well. --target-device=<target> This option specifies the target for which code should be generated. 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. A complete list of supported device names is given in Appendix B. --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 are deleted when the compilation is done. The name of the temporary directory is selected to avoid conflicting with any existing files and directories. The temporary files can be retained using –-keep-files option. In this 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’s interpreted as being relative to the directory containing the project file. --use-batch-file For native mode devices, this option causes the compiler to generate a batch file containing commands to perform the back-end compile-link process instead of building using a makefile. --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. hidden-data 5 Warn about data definitions hiding definitions at outer levels.