|
New Smalltalk/X Release
|
The current Smalltalk/X release 5.4.6 is ready for download on our server. We have fixed more bugs related to the Vista operating system. Also, the Vista-Look was improved. New features are found in the Browser, Debugger, GUI-builder, Bitmap-Editor, Workspace and others. Especially worth mentioning is the Application-Packager, which generates self-installing deployable packages in a few minutes. Of course, all the highlights of the previous releases are also included. |
|
Installation Instructions
Attention !(you can skip this first chapter, if you do not intent to build executables with ST/X):
To avoid later inconveniences when building projects or integrating code from others, we recommend that you unpack the archives into a directory-structure as described below:
...
stxXXX (XXX=Version; z.B. stx542)
stx
libbasic
...
projects
smalltalk
...
...
the intermediate directory "stxXXX" is very useful, if you ever upgrade to the next Smalltalk/X release, and you want to keep multiple releases around (as reference or to your own code around).
Of major importance is however, that you create another directory below that one, BESIDE the"stx" directory. The perfect name for this is your name, initials or company name. Place your individual project directories below that one.
This means:
...
stx542
stx
...
meMyself
project1
...
project2
...
Why should I do so ?
-------------------------------
All clases and methods inside ST/X are associated to a project or package. The package-ID is looks like "xxx:a/b/c", where the "xxx" is the so-called module, and "a/b/c" is called the directory path within the module. All code as delivered with the Smalltalk/X basic system is organized under the "stx" module (i.e."stx:libbasic",
"stx:goodies/demos" etc.).
All make- and build support files assume, that modules are placed side-by-side within the directory hierarchy, and that therefore requried include files such as those within "stx:include" can be found by a regular relaitve path walk. In order to find the include file from within your prohects, these files are referenced via something like "-I../../stx/include".
Obviously, this wil only function correctly, if you have placed your projects in such a way that the parent directory of the "stx" top directory is found by the by moving up n-times via "..".
Similar rules apply for the CVS-Sourcecoderepository, where the module-ID is mapped to a CVSROOT-module. this allows for each module to be stored in a separate repostiory - especially to access the "stx"-tree via our public pserver, and at the same time access your local project files via a local CVS repository.
In addition, this scheme allows for conflict-free integration of code coming from other smalltalkers (as long as they also adhere to this scheme).
Under no circumstances should you place your projects under "stx" or
"projects/smalltalk". because this may make it very hard for you to manage a release upgrade to a new stx version without a lot of manual effort. Especially hard work is to be expected, if there are any naming conflicts due to new files coming from us which are named like yours. Or, if one of your changes in a make- or config-file is lost due to another file coming from with the new release.
Unpacking:
Unpack the ‘.tgz’ file with “tar xvfz xxxx.tgz” or “gunzip < xxx.tgz | tar xvf -”.
Unpack the ‘.zip’ file with “unzip” or “winzip”.
Of course, any other (win)zip unpacker can also be used. or else, double click on the archive to open the archiver.
For all Unix systems, the system-independent parts are included in a separate package “common.tgz”. This must also be downloaded and unpacked in the same directory.
Unix Users (Linux, Solaris, HPUX, S390):
--- Download “common.tgz” and “linux.tgz” to (e.g.) "/tmp"
mkdir stx542
cd stx542
tar xvfz /tmp/common.tgz
tar xvfz /tmp/linux.tgz
During the unpacking process, ignore any messages that refer to files that already exist.
MSDos Users (XP, Vista):
--- Download “win32.zip” to (e.g.) “\temp”
md stx542
cd stx542
unzip \temp\win32.zip
The Windows' ZIP-package includes all files. This means that “common.tgz” is not required. (actually, due to the different line-end conventions, you should NOT unpack the "common.tgz" in an MS-Windows-System)
As the installation procedure provided creates a number of problems on many Windows systems, we recommend that you unpack the archive in an appropriate location and then start it locally in the unpacked directory tree using:
cd projects/smalltalk (backslash under Windows)
smalltalk
Please ignore any INSTALL.sh and INSTALL.bat files (see also below).
Misc:
Unix users will probably want to install ST/X to “/opt/smalltalk” or “/usr/local”. This is possible, but you may have to extend the path variable (PATH) to include “/opt/smalltalk/bin” (i.e. change your “.profile” or “.login” file appropriately). It may be also required to change the value of the LD_LIBRARY_PATH variable, which controls the search for libraries. (Messages stating that a ".so"-file was not found are a a consequence of a wrong or missing LD_LIBRARY_PATH setting. Try "ldd stx" if in doubt).
In Windows, you can create a shortcut to “stx.exe” and/or “winstx.exe” on your desktop. After unpacking, these executables can be found in the subdirectory “projects/smalltalk” or, after installation, in the “bin” subdirectory of the specified target directory. The difference between "stx.exe" and "winstx.exe" lies in the console window, which is opened by the later. In many situations, this enables you to perform some repair work (aka: in case of a crash, you can often type in a repairing Smalltalk-expression to the line-by-line itnerpreter and proceed).
At present, the installation procedure (for Windows) does not create a program group. Therefore, you must enter the applicable menu items manually.
Please also note that “installation” is not really necessary after the files have been unpacked. The INSTALL script simply copies the files to a standard directory and was originally required for installation from a CD. In other words, you can start immediately after the files have been unpacked. No registry entries are required and no system-dlls are replaced.
Deinstallation:Simply delete the entire directory tree (stxXXX/...) or, if you “installed” the files under “/opt/smalltalk” or “\programs\exept”, delete this tree.
Reinstallation or Update to a New Version:Do not unpack or install these files in an existing directory tree. Ideally, you should create a new “stxXXX” directory, where XXX stands for the release number; currently that would be "stx542".
|