If you add this option after the option --project="<path of project file>"
, then the “Enforce signing of compiled libraries” option is enabled in the project in the “Security Screen” on the “User” tab.




NOTICE

When the “Security Screen” is opened and closed again, the current settings are applied in the user options, even when no active changes have been made.
Syntax:
--enforcesignedcompiledlibraries
Example
CODESYS.exe --project="D:\projects\test.library" --enforcesignedcompiledlibraries
Automation Builder.exe --project="D:\projects\test.library" --enforcesignedcompiledlibraries="true"