dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorMenu Commandsdl-breadcrumb-item__separatorMenu 'File'dl-breadcrumb-item__separatorCommand 'Save Project as Compiled Library'
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command 'Save Project as Compiled Library'dl-permalink__symbolPermalink

Function: The command saves a library project in encrypted form.

Call: Menu bar: “File”

The command opens the default dialog for saving a file in the file system. The “Compiled CODESYS Libraries” file type is already preset. The file extension is ‎.compiled-library-v3‎ or ‎.compiled-library‎ (CODESYS < SP15). In this format, then source code of the library POU is not visible when the library is used in a project.

If the “Enforce signing of compiled libraries” option is selected in the “Security Screen” view on the “User” tab, then a library project has to be provided with a digital certificate-based signature when being saved. When a suitable certificate is available, it is provided in the “Security Screen” on the “User” tab in the “Digital Signature” section. In the “Project Information”, on the “Summary” tab, a “Library compatibility” with a CODESYS version >= V3 SP15 is set by default. In this case, the project file is stored with the file extension ‎.compiled-library-v3‎ when being saved as a compiled and signed library. If you still have not specified a suitable valid certificate for your user profile in the “Security Screen”, then a dialog prompt opens next for you to do this. Afterwards, you can execute the save command again.

In all other respects, compiled library files behave just like ‎*.library‎ files, and therefore they can be installed and referenced with the same steps.

We recommend the use of compiled libraries signed with certificates. Besides the protection of the source code and the unauthorized use of a library, less memory is also used which therefore results in shorter loading times.

If you have the corresponding help files with translations, then as of CODESYS V3 SP15 you can extend the library documentation with the translation into other languages. This is done as follows:

Place the files created for the new languages ‎__lmd__<language>.aux‎ in a directory ‎<library name>.lmd‎ parallel to the library project ‎<library name>.compiled-library-v3‎. If the files are correct, then they are included in the compiled library file when saving the library project by means of the “Save Project as Compiled Library” command.

Example: The directory ‎standard.lmd‎ is exists parallel to the library file ‎standard.compiled-library-v3‎ and contains the file ‎__lmd__fr.aux‎ with the French translation of the library documentation. After the compiled library is saved, the French version of the documentation is also available in the Library Manager.