Licensing options for compiled IDL applications
THIS INFORMATION ONLY PERTAINS TO SOFTWARE VERSIONS IDL 8.5, ENVI 5.3 AND PRIOR
Topic:
IDL applications can either be written in IDL itself and distributed as a native IDL *.sav file, or they can be written in an external language that calls IDL routines. In order to run either a native IDL application or an external language application that calls IDL routines, the IDL Runtime environment must initialize in licensed mode. There are three main licensed Runtime modes for IDL: IDL Virtual Machine, IDL-Runtime License, and Embedded IDL License.Discussion:
IDL Virtual Machine (IDL 6.0 and higher):
The IDL Virtual Machine is a freely distributable runtime utility introduced with IDL 6.0. The IDL VM contains all the necessary libraries required to run a commercial or non-commercial *.sav file. Note, however, that certain IDL language features are not available for use with the IDL VM.
Please note that the IDL Runtime environment is still available in IDL 6.0 and is the preferred environment for commercial applications that require functionality not available in the IDL VM.
IDL-Runtime license:
The IDL Runtime Environment contains all the necessary libraries required to run a *.sav file. With an IDL-Runtime license, an IDL application can access IDL functionality not available in the IDL VM. The end user must purchase and configure a runtime license for the system on which the program is run.
IDL Embedded License:
Embedded licensing enables you to build runtime license information into IDL .sav files, callable IDL applications, or IDL ActiveX applications. This *.sav file enables the full IDL-Runtime environment without the need for the end-user to obtain a separate IDL-Runtime License. Since embedded licensing hides the details of licensing to the application end-user, this is an ideal solution for commercial distribution of IDL-based applications. The application developer must purchase embedded licenses from RSI.
When are these licensing options necessary?
Native IDL applications:
A native IDL application is written entirely in IDL and saved in a .sav file or series of .sav files that can be restored an run by an IDL distribution. While SAVE file applications can be run by the full development version of IDL, applications intended to be run as standalone applications can also be run on IDL distributions in one of these additional modes:
- in the IDL Virtual Machine.
- with a runtime license.
- with an embedded license.
External programs that call IDL:
An application that uses Callable IDL is an application written in another programming language, such as C or C++, that calls IDL as a subroutine. The IDL ActiveX control can also be used to access IDL functionality in applications written in other languages that support ActiveX, such as C++ or Visual Basic. Callable IDL applications and IDL ActiveX Control applications are run as standalone applications in one of the following modes:
- with a runtime license.
- with an embedded license.
See these TechTips for additional information on using embedded licensing:
For more information on IDL Application distribution options, please contact your sales representative. For more information on creating IDL applications, please consult the Building IDL Applications manual, located in the IDL on-line documentation.Solution:
[Edit this field in the IDL-based Tech Tip Editor, v3]