Next Previous Contents

1. Installation

This release has been tried on Linux (Fedora, Ubuntu, etc.), Mac OS X, Irix and Windows.

partiview needs two libraries to compile: OpenGL (or MESA) for the drawing operations, and FLTK for the graphical user interface. These libraries are known to work on MS-Windows as well as many Unix flavors.

1.1 OpenGL (possibly via Mesa)

Most platforms will have it installed already, whether as libMesaGL or libGL. Our configure script (see below) should take care of the two possible options.

Homepage: http://mesa3d.sourceforge.net/

Redhat packages: (part of powertools I believe)

1.2 FLTK

Also make sure FLTK is installed, from fltk.org. FLTK versions 1.3.x work. FLTK 2 will not work with partiview.

If you're not sure whether you already have it, try


       % locate libfltk.a 
       % locate Fl_Slider.h

if they fail, then

       % cd <where-ever>/fltk-1.3.0
       % make install
  

(you only need it if you want to recompile partiview at some point, not if you just want to run it, since FLTK is built-in to partiview binaries.)

Homepage: http://www.fltk.org/

Find rpms: http://rpmfind.net

FLTK is under continuous development. Versions from 1.1.1 through 1.1.9 have been successfully tested with partiview. Some problems with other versions exist, but 1.1.4 is also known to work.

1.3 partiview

You can decide to use a branded version, usually available as a tar or zip file, or use the CVS (see below). Extract the tarball, and install the program from within the src directory:


       % tar zxf partiview-0.6.tar.gz

       % cd partiview-0.6/src
       % make clean                (if you really must compile a new executable)
       % ./configure               (GNU autoconf toolset to ease installation)
       % make depend               (might need to make new local dependancies)
       % make partiview            (should not have to edit Makefile anymore)

If you encounter difficulties of locating either the FLTK or MESA/OpenGL libraries, configure script options can specify them: --with-fltk=dirname names the directory which contains the lib and FL subdirectories, --with-mesa=dirname can specify the Mesa installation directory [??], and --with-kira=dirname names the Starlab directory, whose default value is taken from environment variable STARLAB_PATH if that is set.

1.4 CVS

The current source code of partiview is always available from CVS, with public anonymous read-only access. Occasionally we stamp out a packaged release, too, but looking to CVS is best.

(Partiview developers can request a non-anonymous CVS account from Peter Teuben -- teuben@astro.umd.edu.)

Currently the CVS repository machine is cvs.astro.umd.edu. Here's a sample session with some commonly used CVS commands:


 export CVSROOT=":pserver:anonymous@cvs.astro.umd.edu:/home/cvsroot"
 export CVSEDITOR=emacs

 cvs -d :pserver:anonymous@cvs.astro.umd.edu:/home/cvsroot  login
                                     # only needed once, to set up "pserver" CVS access

 cvs -d :pserver:anonymous@cvs.astro.umd.edu:/home/cvsroot checkout partiview
                                     # get a new local sandbox to work in, or

 cd partiview                        # goto the root directory of partiview
 cvs -n -q update                    # check if others had made any changes
 cvs update                          # if so, update your sandbox and/or resolve conflicts

 cd partiview/src                    # goto the 'src' directory of partiview
 ./configure --with-fltk=/some/where/fltk-1.3.something/ --with-glew=/some/where/glew...

 emacs partibrains.c                 # edit some files
 make all                            # compile the program
 ./partiview                         # test the program
 emacs kira_parti.cc                 # edit another file
 make all                            # check if it still compiles

 cvs -n -q update                    # check if anybody else made changes
 cvs update                          # if so, update your sandbox again, resolve conflicts

 cvs commit                          # and commit your changes

1.5 Compiling under Windows

Partiview can be compiled from the command line on Windows using gcc/g++ with MinGW32, MSYS and w32api (see http://mingw.org/). The MinGW route is currently the only way to compile with kira/Starlab support. There's no provision for building partiview within the MS Visual Studio GUI. Mingw64 has not been tested, only Mingw32.

To compile with MinGW and company, you'll need to:

  1. Install MinGW (gcc, etc.), and the MSYS suite of UNIX-like tools. It's easiest to simply fetch and run the mingw installer. See the Download link in: http://mingw.org
  2. Install into a directory such as C:\MinGW.
  3. Open a MinGW shell: invoke msys.bat, which will be under something like C:\MinGW\MSys\1.0\msys.bat.
  4. Use MinGW to build FLTK. (FLTK 1.3.x, e.g. 1.3.0, works with partiview. FLTK 2.0 won't work. Not sure about versions in between.) Unpack the FLTK source distribution and say
        sh configure
        make
    
  5. Build the Starlab libraries, if desired:
    1. Use CVS to checkout the Starlab sources into some directory:
          cd C:\some\where
          set CVSROOT=:pserver:anonymous@cvs.astro.umd.edu:/home/cvsroot
          cvs login
          cvs checkout starlab
          cd starlab
      
    2. Copy templates\starlab_setup.bat to local\starlab_setup.bat, and edit it. Change the first two set commands: set STARLAB_PATH to the installation directory -- in the above example, set STARLAB_PATH=C:\some\where\starlab. Also optionally update (or remove) set PATH=... to add MSYS and MinGW bin directories to it.
    3. From a Windows command window, type
           local\starlab_setup
           make libs  
      
    4. If successful, you should find in the lib directory the files libdstar.a libdyn.a libnode.a librdc.a libsstar.a libstd.a libtdyn.a
  6. Now, back in the partiview/src directory, use configure and make as under Unix. The MSYS package imposes its own UNIX-like syntax for Windows pathnames, which you'll need to use as arguments to configure and friends, with forward- instead of backslashes and a /drive-letter prefix. Also, if typing to a Windows command-window, shell scripts like configure must be explicitly fed to sh. Thus for example if FLTK is installed in C:\util\fltk-1.1.9 and Starlab is in F:\src\starlab, then you might build partiview by typing
            sh configure --with-fltk=/c/util/fltk-1.3.0  --with-kira=/f/src/starlab
            make
    
    Note there's no need to specify the location of the OpenGL or other libraries; the configure script and MinGW tools already know where to find those. Omit the "--with-kira=..." if you're not using Starlab.


Next Previous Contents