Microchip Technology XC8 Standard Compiler (Workstation) SW006021-1 SW006021-1 User Manual
Product codes
SW006021-1
MPLAB
®
XC8 C Compiler User’s Guide
DS52053B-page 114
2012 Microchip Technology Inc.
4.8.51
--SCANDEP: Scan for Dependencies
When this option is used, .dep and .d dependency files are generated. The depen-
dency file lists those files on which the source file is dependant. Dependencies result
when one file is #included into another. The .d file format is used by GCC-based
compilers and contains the same information as the .dep file.
dency file lists those files on which the source file is dependant. Dependencies result
when one file is #included into another. The .d file format is used by GCC-based
compilers and contains the same information as the .dep file.
Compilation will stop after the preprocessing stage if this option is used.
4.8.52
--SERIAL: Store a Value At This Program Memory Address
This option allows a hexadecimal code to be stored at a particular address in program
memory. A typical task for this option might be to position a serial number in program
memory.
memory. A typical task for this option might be to position a serial number in program
memory.
The byte-width of data to store is determined by the byte-width of the hexcode param-
eter in the option. For example, to store a one byte value, 0, at program memory
address 1000h, use --SERIAL=00@1000. To store the same value as a four byte
quantity use --SERIAL=00000000@1000.
eter in the option. For example, to store a one byte value, 0, at program memory
address 1000h, use --SERIAL=00@1000. To store the same value as a four byte
quantity use --SERIAL=00000000@1000.
This option is functionally identical to the corresponding HEXMATE option. For more
detailed information and advanced controls that can be used with this option, refer to
Section 8.6.1.15 “-SERIAL”.
detailed information and advanced controls that can be used with this option, refer to
Section 8.6.1.15 “-SERIAL”.
The driver will also define a label at the location where the value was stored, and which
can be referenced from C code as _serial0. To enable access to this symbol,
remember to declare it, for example:
can be referenced from C code as _serial0. To enable access to this symbol,
remember to declare it, for example:
extern const int _serial0;
See Section 4.9 “MPLAB IDE V8 Universal Toolsuite Equivalents” or
Section 4.10 “MPLAB X Universal Toolsuite Equivalents” for use of this option in
MPLAB IDE.
Section 4.10 “MPLAB X Universal Toolsuite Equivalents” for use of this option in
MPLAB IDE.
4.8.53
--SETOPTION: Set the Command-line Options For Application
This option is used to supply alternative command line options for the named
application when compiling. The general form of this option is: as follows.
application when compiling. The general form of this option is: as follows.
--SETOPTION=app,file
where the app component specifies the application that will receive the new options,
and the file component specifies the name of the file that contains the additional
options that will be passed to the application. This option is not required for most
projects.
and the file component specifies the name of the file that contains the additional
options that will be passed to the application. This option is not required for most
projects.
If specifying more than one option to a component, each option must be entered on a
new line in the option file. This option can also be used to remove an application from
the build sequence. If the file parameter is specified as off, execution of the named
application will be skipped. In most cases, this is not desirable as almost all applications
are critical to the success of the build process. Disabling a critical application will result
in catastrophic failure. However, it is permissible to skip a non-critical application such
as CLIST or HEXMATE if the final results are not reliant on their function.
new line in the option file. This option can also be used to remove an application from
the build sequence. If the file parameter is specified as off, execution of the named
application will be skipped. In most cases, this is not desirable as almost all applications
are critical to the success of the build process. Disabling a critical application will result
in catastrophic failure. However, it is permissible to skip a non-critical application such
as CLIST or HEXMATE if the final results are not reliant on their function.
4.8.54
--SHROUD: Obfuscate P-code Files
This option should be used in situations where either p-code files or p-code libraries
are to be distributed and are built from confidential source code.
are to be distributed and are built from confidential source code.
C comments, which are normally included into these files, as well as line numbers and
variable names will be removed, or obfuscated, so that the original source code cannot
be reconstructed from the distributed files.
variable names will be removed, or obfuscated, so that the original source code cannot
be reconstructed from the distributed files.