Next: , Previous: , Up: Top   [Contents]


6 Managing Extended Runtime License Information

Extended runtime systems need to have a license available at runtime. This license can be embedded in the extended runtime executable or located in a separate file. The following describes the steps needed in order to enter the license information. The example assumes that you are familiar with the procedure for building runtime systems. See The Application Builder in the SICStus Prolog Manual for details.

Suppose that you have been provided with the following license information:

Dear SICStus Prolog customer,

Your extended runtime license information for platform 'PLATFORM' is as follows:

Site name:          MySite
License code:       a111-b222-c333-d444-e444
Expiration date:    permanent

Corresponding to a file 'extended_license.pl' with the following contents:
%% LICENSE BEGIN
site('MySite').
product('extended_runtime_sicstusMAJOR.MINOR_PLATFORM',
       'permanent',
       'a111-b222-c333-d444-e444').
%% LICENSE END

Please note: The license information differs between SICStus versions and platforms. The PLATORM is one of win32 (for Microsoft Windows), linux, darwin (for Apple macOS), or solaris. The MAJOR.MINOR is the major and minor version of SICStus, currently 4.7.

Following is a list of common tasks.



Send feedback on this subject.