2. Installation

The VEGA package is available in different archives:

Vega_XX_Irix6.2.tar.gz

SGI IRIX 6.x executable.

Vega_ZZ_XX_x86-x64.exe

Windows x86 (32 bit) and x64 (64 bit) OpenGL setup wizard.

Vega_XX_Linux_86-32.tar.gz

Linux x86 (32 bit) executable.

Vega_XX_Linux_86-64.tar.gz Linux AMD64 (64 bit) executable.

Vega_XX_Amiga.lha

AmigaOS 68k executable.

Vega_XX_Locale.tar.gz Localization toolkit with FlexCat compiler.

Vega_XX_Source.tar.gz

ANSI C source code, localization toolkit and utilities.

where XX is the release number of each archive. You you can download only the package for your system, because each archive contains all the files needed, but not the source code that is provided in a separate archive.

 

2.1 Unix installation

This section of the manual shows the steps needed to install the VEGA package on Unix-like operating systems (e.g. IRIX, Linux, NetBSD, etc). If your operating system is not directly supported by Authors, you must download and compile the source code (Vega_XX_Source.tar.gz archive).

 

2.1.1 Building the VEGA package

The high portable source code allows to build the package virtually for any computer platform that has a standard ANSI C compiler. It is possible to find some minor compiling problems due to hardware differences. If you can’t solve these problems, please contact the Authors.

As first step, you must unpack the Vega_XX_Source.tar.gz file, using the gzip command. If this command is not available in your system, you can download it from any GNU software archive (see: http://www.opensource.org). The correct syntax is:

gzip –d Vega_XX_Source.tar.gz

the unpacked file (Vega_XX_Source.tar) created by gzip must be dearchived with tar command:

tar –xvf Vega_XX_Source.tar

A directory called Vega will be created.

Check if the libraries libbz2.a, loblocale.a, libxdrf.a, libz.a and libZ32.a are present in the directory ...Vega/Src/Vega/MySO where MySO is the directory of your operating system. If not, you must compile these external libraries using the sources placed respectively in ...Vega/Src/Bzip2, ...Vega/Src/LocaleLib, ...Vega/Src/XdrfLib, ...Vega/Src/Zlib and ...Vega/Src/Z32 editing the Makefile and running make. Each library must be copied in ...Vega/Src/Vega/MySO.

After this operation, change your current directory in ...Vega/Src/Vega/MySO (Amiga, Irix, Linux, Unix, Win32) and, if needed, edit the Makefile with your preferred program. Some remarks can help you in this operation. Please set the CC variable to the compiler name (usually cc or gcc) and the CFLAGS variable for the best optimization (e.g. –O –s).

At this point, run make and the VEGA executable is compiled for your system. The makefile was successfully tested with SGI cc and GNU C (gcc for Linux, gcc for AmigaDOS) compilers.

Warning:
Starting from the 1.5.0 release, it was introduced the use of 64 bit integers to speed-up the manipulation of 8 character strings and thus to build VEGA, it's required a C compiler that supports that integer size. 

 

2.1.2 Setting-up your Unix system

If the downloaded package has been specifically developed for your operating system, you must unpack it using the following two commands:

gzip –d Vega_XX_MyOS.tar.gz

tar –xvf Vega_XX_MyOS.tar

If you have GNU tar, you can even do it in one step only:

tar Zxvf Vega_XX_MyOS.tar.gz

Please note that the pathway where the archive has been unpacked, is the real installation path.
The next step is the editing of your shell start-up script (e.g. .cshrc for csh or tcsh, .bashrc for GNU bash) in order to set VEGADIR and the LD_LIBRARY_PATH environment variables to the installation path. For csh/tcsh shell, you must type:

setenv VEGADIR "<INSTALLATION_PATH>"
setenv LD_LIBRARY_PATH "$LD_LIBRARY_PATH:$VEGADIR"
setenv PATH "$PATH:$VEGADIR"

For sh/bash:

export VEGADIR="<INSTALLATION_PATH>"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$VEGADIR"
export PATH="$PATH:$VEGADIR"

The LD_LIBRARY_PATH is requeired to inform your system where are the dynamic libraries needed by VEGA. It’s strongly recommended to add the installation directory pathway in the command search variable path, defined in the shell startup script.

For example, if you installed VEGA in the /usr/local/bin/vega directory, you must set the environment variables as follow (csh/tcsh):

setenv VEGADIR "/usr/local/bin/vega"
setenv LD_LIBRARY_PATH "$LD_LIBRARY_PATH:$VEGADIR"
setenv PATH "$PATH:$VEGADIR"

or (sh/bash):

export VEGADIR="/usr/local/bin/vega"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$VEGADIR"
export PATH="$PATH:$VEGADIR"

Finally, you must change the file permissions:

chmod 755 $VEGADIR/vega
chmod 755 $VEGADIR/inpmerge
chmod 755 $VEGADIR/sqlite3
chmod 755 $VEGADIR/top2tem

As option, edit the <INSTALLATION_PATH>/Data/prefs file, find the <LANGUAGE> item  and select your preferred language (at this time, two languages are supported only: english and italian). The automatic language selection isn't supported with Unix operating systems.

 

2.2 Windows installation

This release contains two versions: the console (command line) and the ZZ (OpenGL) versions. The first is a true Win32 console application and thus can’t be executed under Ms-Dos or Windows 3.x operating systems. It supports correctly long filenames and works fine with Windows 95, 98, NT, 2000, XP, Server 2003 and Vista operating systems (x86 and x64 editions). The package has been compiled using the standard Pentium ® instruction set. In order to increase the performances, the code can be optimized with P6 instruction set (Pentium ® Pro, II, III and AMD K6 ®), simply recompiling the package. The second version is a powerful application with an enhanced graphic interface. For more information, go to VEGA ZZ section.
To install the Vega_XX_x86-x64.exe package, you must execute this file and follow the simple installation wizard. Please note that only the uninstall information are added in Windows registry. If your operating system is greater than Windows 98, you must have the administrator rights.
If your system has got a software firewall, you must configure it granting the network access to REBOL.exe, otherwise the scripting system doesn't work because it uses the standard TCP/IP communication ports.
After the installation, run VEGA ZZ and the activation procedure starts.

Warning:
Installing VEGA ZZ on x64 operating systems (e.g. Windows XP Professional x64 Edition, Windows Server 2003 x64 Editions and Windows Vista x64 Editions), some executables are replaced by their 64 bit versions and so it might be possible to use different file names to run them (e.g. Vega64.exe instead of Vega.exe). The estimated performance boost provided by the 64 bit executables is more than 20% with AMD CPUs. The same performance improvement is not guaranteed if a Intel EM64T CPU is installed.

 

2.2.1 About the TurboPack

The TurboPack is a sub-package that contains DLLs for a specific CPU in order to obtain the maximum performance from your hardware system. The setup wizard allows to select the installation of four TurboPack versions:

TurboPack 686    for Intel Celeron, Pentium Pro, Pentium II, Pentium III and Xeon.
TurboPack P4 for Intel Pentium 4.
TurboPack K7 for AMD Duron, Athlon (4, XP and MP).
TurboPack K8   for AMD Opteron, Athlon 64/FX and Sempron.

The TurboPack 586 is installed by default. If you don't know your CPU type, install all TurboPacks because VEGA can  automatically load the more efficient DLLs for your CPU.

 

2.3 AmigaDOS installation

System requirements needed to run the AmigaDOS version of VEGA:

To install this version of VEGA package, you must unpack the distribution archive using lha command from the command shell:

lha x Vega_XX_Amiga.lha

A directory called Vega will be automatically created. If you don’t have lha, you can download it from Aminet. As for Unix systems, you must add in the user-startup file (placed in s directory of your boot disk) the following line:

SetEnv VEGADIR <INSTALLATION_PATH>

Instead of the user-startup modification, you can create a new text file in ENVARC: directory containing a single line with the installation pathway. Starting from 1.2 release, this installation step is needed only if VEGA executable is placed in a directory that is not the installation folder.

If you want to add VEGA to your standard command pathway, you can add in the user-startup the following line:

Path <INSTALLATION_PATH> Add

As final step, reboot your computer. Please note that VEGA for Amiga can accept AmigaDOS and Unix-like pathway specification. Use the specific VEGA version for the CPU installed in your system:

Version CPU
VEGA.000 68000, 68010 and any other CPU without FPU.
VEGA.020 68020 and 68030 with 68881/2 FPU.
VEGA.040 68040 and 68060.

The PowerPC CPUs aren't supported.