Packaging a Smalltalk image
You deploy your project from the workstation to another platform by way of
packaging. Once the project is ready to be delivered to a target platform, you use the packaging process to create a runtime image according to a set of
packaging rules. These rules are a combination of a standard set associated with the development tools and a set that you define. The results of the packaging process contain only the objects it needs to run in its intended environment.
VA Smalltalk Server allows you to package your Smalltalk image into a single module or as part of a dual module configuration. The next few pages describe the
steps to take in the process of packaging.
This section uses the following terms:
Development image
The image that you interact with, typically through a graphical user interface (GUI) that contains the development tools and environment.
Passive image
The image containing the set of Smalltalk applications and classes that are targeted to be run in an environment other than the development environment.
Current image
The image on which all tools are currently set to operate. There can only be one current image at any time. During development, the current image is normally the development image. When packaging for a target environment, the current image will be the appropriate passive image.
Runtime image
The packaged image that can be run on the target platform.
Packaging instruction
The object used to control the build process without becoming part of the delivered project. The packaging instruction is analogous to the 3GL concept of a makefile or a build script.
Last modified date: 05/09/2019