libGiST v.0.9b1 Installation Notes

Portability

libGiST was concurrently developed under HP/UX with the g++ compiler, and under Windows NT with the Microsoft Visual C++ 4.1 compiler. It is also reported to have ported cleanly under Solaris with g++. Since these platforms are quite different, we expect the code to be quite portable, but have not done extensive porting ourselves. Before you port libGiST to other platforms, please check the libGiST home page and see if anyway has done it for you already. If not, and you succeed in porting, contact us at gist@postgres.berkeley.edu!

NT Installation Notes

Requirements

• Either an unzip package, or tar and gunzip. All of these are widely available on the web.
• Microsoft Visual C++ version 4.1: earlier versions may work, but we make no guarantees
• Microsoft Developer Studio: not strictly necessary, but you will have to create your own NMAKE files if you don't have Developer Studio
• bison & flex: not actually required for libGiST, but necessary to use the demonstration code. bison and flex for Windows are freely available on the Web from a variety of sources.

Procedure

1. Run the genparse.bat script in the topmost directory.
2. Load libGiST\libGiST.mdp into Developer Studio. You probably want to build both the Debug and Release configurations.
3. For each demo project of interest, there is a .mdp file in the directory that can be loaded into Developer Studio to build the demo applications.
4. Libraries and executables will be left with their sources.  If you wish to install them elsewhere, you will need to do so by hand.

UN*X Installation Notes

Requirements

• Either an unzip package, or tar and gunzip. All of these are widely available on the web.
• g++ version 2.7.2: other versions may work, as may other C++ compilers, but we have not tested any.
• gmake: you may substitute make, but will need to rewrite the (simple) Makefiles to suit.
• bison & flex: not actually required for libGiST, but necessary to use the demonstration code. bison and flex are freely available on the Web from a variety of sources. It is possible that yacc and lex may be substituted, but we have not tested them.

Procedure

1. Edit the top-level Makefile, and set paths for the various tools, etc.
2. Run gmake -- it will recursively make libGiST and all the example projects.
3. Libraries and executables will be left with their sources.  If you wish to install them elsewhere, you will need to do so by hand.

Comments, questions and suggestions may be directed to gist@postgres.berkeley.edu