To package your application into a shrink-wrapped executable file, do the following:
If you select None, make sure that the application class has a class method that provides startup logic. For information on startup logic, refer to descriptions of the method runtimeStartUp in materials on packaging in the IBM Smalltalk User's Guide .
You can only include as prerequisites applications that you make and applications that IBM permits you to redistribute. For a list of redistributable applications, refer to the online .api file.
Note: | One way to see if your application names the correct prerequisites is to check messages printed to the System Transcript. If you see the message #<method>: should not reference <class>, the application you are working with needs to add a prerequisite. The application containing the class named in the message is what you should add as the prerequisite. |
If VisualAge finds methods that reference global variables or classes that don't exist in your application, it informs you that it found "packaging problems" and opens a Packager Reference control panel that lists the problems. Later, you can come back to this browser, change your application to resolve the problems, and try packaging again. If none of the problems listed refer to methods in your application, packaging is complete. Select Cancel.
Any .MPR, .DLL, or other files used by your application. For OS/2 and Windows, you might need to copy ESVM40.DLL, plus other DLL files, to the directory if your system's environment variables cannot find the file.
<base .IMG and executable file name>
That is, if you specified MYAPP.ICX for the packaged image name and the startup executable has MYAPP in its name, enter
myapp
on Windows or OS/2. On UNIX, enter
myapp&
Your (main) visual part should open, like when you click on
For more details on packaging, refer to the following: