Skip to main content

Dialog: Project Settings – Compile options

Symbol: _icon_compile_option.png

Function: Provides information about the compiler version and configures compile options project-wide

Call: Project → Project Settings command, Compile options category

Requirement: A project is open.

Table 140. Compiler Version

Fix version

Shows the compiler version which is used when compiling and when loading for compiling.

An update to the newest compiler version is possible, but resetting to an older version is not possible.



Table 141. Settings

Allow Unicode characters for identifiers

Cleared by default because using Unicode characters in identifier names is not permitted in the IEC standard

May be required for some foreign languages (example: Asian languages)

Replace constants

_cds_icon_checked.png: (default) The value is loaded directly for every scalar constant (not for STRING, ARRAY, or structures).

In online mode, the constants are marked with a symbol which is prepended to the value in the declaration editor or monitoring view. In this case, access is not possible, for example by means of an ADR operator, forcing, and writing.

_cds_icon_option_deactivated.png: Access to constants is possible, but it prolongs the computation time.

Enable logging in breakpoints

For breakpoints which are defined as execution points, you can create a message text in the Execution Point Settings dialog. This text is printed to the device log when the application halts at the execution point.

UTF8 Encoding for STRING

_cds_icon_option_deactivated.png: Strings with the STRING data type are encoded in ASCII format project-wide. An index access to the literal works properly.

_cds_icon_checked.png: Strings with STRING data type are encoded in UTF-8 format project-wide. This applies to every STRING literal and is also used for their monitoring.

Index access to the UTF-8 literal is not advisable and will mostly lead to errors.

Tip

If project-wide encoding to UTF-8 format is not desired, a single variable type can be implicitly converted with a UTF8# prefix.

UTF-8 encoding only for project-wide configuration

A UTF-8 encoding is used if the project-wide compile option UTF8 encoding for STRING is enabled. Library functions and add-ons are then also oriented according to this setting.

If you use single UTF-8 encoded strings, then you need to make sure that they are interpreted correctly wherever they are used. For example, a string variable in the OPC server will be converted to UTF-8 before being transferred to a client if the setting is not selected. Values such as UTF8#'äöü' would then be misinterpreted. Similar problems can arise when outputting strings in the visualization.

Edit Project Defines

Opens the Edit Project Defines dialog.



Table 142. Compiler Warnings

Maximum number of warnings

Refers to the warnings which are output to the message view

Tip

You define the selection of displayed compiler warnings in the Project Settings dialog, in the Compiler warnings category.



Table 143. Dialog: Edit Project Defines

Add Project Define

Adds a new row to the table. Double-click this row to open the line editor and enter the identifier for the new project define. The new project define has to be a valid IEC identifier.

The project defines are valid throughout the entire project and in all referred libraries. They do not apply in public interfaces.



For more information about project defines, see: project_defined (<global define>)

: