The following sections describe the steps you must perform prior to distributing your application on UNIX systems. For information on distributing your application on Microsoft Windows systems, see Preparing a Windows Distribution.
The method for preparing an IDL distribution varies depending on the type of IDL application you are distributing:
If your native IDL application is intended to be run in an existing fully-licensed IDL installation, you do not need to create an IDL distribution. Simply package up your application files (either
.pro files or
.sav files, and any necessary data files) and distribute it to your users along with instructions describing how to install and launch the application.
If your IDL Virtual Machine application is intended to be run in an end-user's existing IDL installation, you do not need to create an IDL distribution. Simply distribute the
.sav files that make up your application along with instructions on how to install and launch the application. SAVE files created to be run in the IDL Virtual Machine can be placed anywhere on the user's system, and launched as described in Running a .sav File in the IDL Virtual Machine.
The following steps are required before distributing a Callable IDL application.Add Your Executables to the Distribution
Copy your application executable to the
bin.platform directory, where platform is the name of the platform for which you created the application. If you are distributing your application on multiple platforms, copy the executable for each platform to the corresponding
bin.platform directory. Placing your executables in the
bin.platform directory offers a couple of advantages:
bindirectory. This script is designed to start the correct executable, depending on the platform on which it is being executed. This allows the user to start the application on any platform by simply executing the startup script in the top-level directory, thereby saving the user from having to know the directory in which the executable is located.
Located in the
bin directory of your distribution is a script called
idl. For Callable IDL applications, this script must use the same name as your application executable in the
bin.platform directory. For example, if your application executable in the
bin.platform directory is called
myapp, rename the
idl script in the
bin directory to
In the top-level directory of your application distribution, there is a startup script with the name specified by the
savefile parameter you specified when you ran the
make_rt script. Make the following changes to this script:
bindirectory that you renamed in the previous section, Rename the idl Script. For example, if your application executable in the
bin.platform directory is called
myapp, and you therefore renamed the
idlscript in the
myapp, you would edit the startup script in the top-level directory as follows:
bindirectory. See the example after the following step.
If there are other RSI products installed on the user's machine, IDL_DIR may already be set. For this reason, IDL_DIR should be set for the instance of the shell that will be used to start your application, but should not be set in the user's login scripts such as
.profile. This allows IDL_DIR to be set properly for your application, without conflicting with the IDL_DIR setting for other products the user may have installed.
The most convenient way to set IDL_DIR on the user's machine is to have your installation script (or the user) edit the startup script. This saves the user from having to manually set IDL_DIR prior to launching your application. You can either provide the user with instructions on adding the necessary commands to the startup script, or you can have your installation script modify the startup script. For example, if an application called
myapp is installed in the
/home/apps directory, your startup script would resemble the following:
IDL_DIR=/home/apps export IDL_DIR /home/apps/bin/myapp
If you do not modify the startup script, the user must set IDL_DIR at the command prompt prior to launching your application. For example, if your application is installed in the user's
/home/myapp directory, the user could execute the following command at the C shell prompt:
setenv IDL_DIR /home/myapp
For both IDL and Callable IDL applications, starting your application on UNIX requires the following steps: