Check that in SAS_DIR there is the file: RELEASE. It should contain the name of the release. The name of the release should correspond to name of a SAS manifest.
Create a target directory where the binary files will be copied. In the following that directory is called `installdir`.
cd $SAS_DIR
make binary_install PREFIX=$installdir
This last command makes a piped-tared copy of the relevant SAS directories and files. You'll get warning messages if some of the links in bin doc etc. are stale. The stale links are not transfered to $installdir.
A quick test of the binary SAS can beperformed:
export SAS_DIR=$prefix
. $SAS_DIR/sas-setup.sh
sas
The gui should appear and it should be possible to run SAS tasks.
Optionally, some clean up can be performed:
rm -f $SAS_DIR/lib/lib*.a
find $SAS_DIR/ -name Makefile -exec rm {} \; -print
find $SAS_DIR/ -name notest -exec rm {} \; -print
Some Makefile and notest are there because they are in a directory symlinked to from TOPDIR.
Now tar it up:
cd ..
tar -czfv $SAS_DIR $SAS_DIR.tgz
Now copy the auxiliary libraries (shared versions) in
$SAS_DIR/libextra. What libraries need copying depends on what shared
libraries were in use during the build. The current list is:
cp /pacth/to/libstdc++.so.2.9.0 $SAS_DIR/libextra
cp /pacth/to/libqt.so.2 $SAS_DIR/libextra
cp /pacth/to/libpgplot.so $SAS_DIR/libextra
And make a second tar file like this:
tar -cvzf $SAS_DIR/libextra $SAS_DIR_libextra.tgz
Copy the two tar files to the ftp site, update download.html on the web.