Problems during packaging
Output file path
If you specify a fully qualified path to the Output File on the Output Image page of the packager control panel, then VA Smalltalk packager expects the directory that you have specified to exist. If it does not exist, the output image operation will fail and a dialog will inform you that the directory does not exist.
To solve the problem either change the Output File specification or create the directory. Then press the Output Again button on the Output Image packager notebook page to attempt the output operation again.
Saving your image
If you find that the size of your saved development image is much larger than when you started, and you have used it primarily for packaging, you might have saved your image with the Packager Control Panel open. As a result of doing this, you will also be saving the in memory packaging instruction objects. Each in memory packaging instruction and related objects can occupy up to two megabytes of memory and disk space in the image.
To alleviate the problem either discard the instructions in memory or close the Packager Control Panel.
If you find that the development image has lost the externalized strings, you may have saved your image after running the packager.
To alleviate the problem, discard the abt.icx file and get a new one. Environments is the easiest way to do this.
Duplicate object error when packaging
The most common cause of this is a class which is referenced in an application, but the definition of the class is not in the prerequisites of the application in which the reference is made. As a result, a class name appears in two separate name spaces (applications), and the packager is attempting to dump two different classes which have the same name.
To solve the problem, find the Application in which the class is defined, and then add that Application to the preqequisites in the Application which references the class. Version and release before returning to packaging.
Last modified date: 04/26/2019