dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorMenu Commands dl-breadcrumb-item__separatorFile 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

Function: The command saves a library project in an encrypted format.

Call: “File” menu

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 < V33.5 SP15). In this format, the 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 >= V33.5 SP15 is set by default. In this case, the project file is saved with the ‎.compiled-library-v3‎ file extension when it is 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 run 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 that you use libraries which are compiled and 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 in CODESYS V V33.5 SP15 and later you can extend the library documentation with the translation into other languages as follows:

Place the ‎__lmd__<language>.aux‎ files created for the new languages in a ‎<library name>.lmd‎ directory parallel to the ‎<library name>.compiled-library-v3‎ library project.

If the files are correct, then they are included in the compiled library file when the library project is saved by means of the “Save Project as Compiled Library” command.

Example: The ‎standard.lmd‎ directory exists parallel to the ‎standard.compiled-library-v3‎ library file and contains the ‎__lmd__fr.aux‎ file 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.

For more information, see: ⮫ “Information for Library Developers ” and ⮫ “Command: Save Project and Install in the Library Repository ”