<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Partiview (PC-VirDir): Installation</TITLE>
 <LINK HREF="partiview-2.html" REL=next>

 <LINK HREF="partiview.html#toc1" REL=contents>
</HEAD>
<BODY>
<A HREF="partiview-2.html">Next</A>
Previous
<A HREF="partiview.html#toc1">Contents</A>
<HR>
<H2><A NAME="s1">1. Installation</A></H2>

<P>
<P>This assumes you have the October 2000 release (version 0.1 or later) of 
<B>partiview</B>, not the earlier "<B>gview</B>" release that was described
in earlier versions of this document. We keep copies of some support
files (Mesa, FLTK) on our initial
<A HREF="http://www.astro.umd.edu/nemo/amnh">http://www.astro.umd.edu/nemo/amnh</A> website. Note that
this current development release is only documented for work under Linux,
although we expect it to work for at least SGI and maybe Solaris too.
<P>
<H2><A NAME="ss1.1">1.1 MESA/OpenGL</A>
</H2>

<P>First make sure <CODE>Mesa</CODE> is installed, for <CODE>redhat6.2</CODE>
there are rpm files
available.  Check if you have the following:
<P>
<BLOCKQUOTE><CODE>
<HR>
<PRE>
       % rpm -qa | grep Mesa
       Mesa-3.2-2
       Mesa-devel-3.2-2
       % rpm -i Mesa-3.2-2.i686.rpm Mesa-devel-3.2-2.i686.rpm
</PRE>
<HR>
</CODE></BLOCKQUOTE>
<P>You should have both installed. Some packages will use <CODE>libMesaGL</CODE>, others
<CODE>libGL</CODE>. The <CODE>configure</CODE> script (see below) 
should take care of the two possible options.
<P>Homepage: 
<A HREF="http://mesa3d.sourceforge.org">http://mesa3d.sourceforge.org</A><P>Redhat packages: (part of powertools I believe)
<P>
<H2><A NAME="ss1.2">1.2 FLTK</A>
</H2>

<P>Also make sure <CODE>fltk</CODE> is installed.  If you got my version, do this (as
root)
<P>
<P>
<BLOCKQUOTE><CODE>
<HR>
<PRE>
       % locate libfltk.a 
       % locate Fl_Slider.h

       % cd &lt;where-ever>/fltk-1.0.9
       % make install
  
</PRE>
<HR>
</CODE></BLOCKQUOTE>
<P>(you only need it if you want to recompile the program at some point,
not if you just want to run it)
<P>Homepage: 
<A HREF="http://www.fltk.org/">http://www.fltk.org/</A><P>Redhat packages: 
<A HREF="http://www.cs.cornell.edu/nogin/RPM/fltk-devel.html">http://www.cs.cornell.edu/nogin/RPM/fltk-devel.html</A><P>
<H2><A NAME="ss1.3">1.3 partiview</A>
</H2>

<P>
<P>Extract the tarball, and install the program from within the 
<CODE>src</CODE> directory:
<P>
<BLOCKQUOTE><CODE>
<HR>
<PRE>
       % tar zxf partiview-0.5.tar.gz

       % cd partiview-0.5/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)
</PRE>
<HR>
</CODE></BLOCKQUOTE>
<P>
<H2><A NAME="ss1.4">1.4 CVS</A>
</H2>

<P>Since <CODE>partiview-0.3</CODE> is under CVS control, and occasionally we
will stamp out a new release when we deem it stable. Anonymous CVS may also
be offered, but this is not currently enabled. Currently the 
CVS repository machine is
<CODE>grus.astro.umd.edu</CODE> and you will need to setup your developers account with
Peter (<CODE>teuben@astro.umd.edu</CODE>). Here's a sample session with some commonly
used CVS commands:
<P>
<BLOCKQUOTE><CODE>
<HR>
<PRE>
 setenv CVSROOT   :pserver:pteuben@grus.astro.umd.edu:/grus/cvsroot
 setenv CVSEDITOR emacs
 setenv CVS_RSH   ssh           (not needed for pserver access though)

 cvs login                      (only needed once, and only for pserver type access)

 mkdir ~/cvsstuff
 cd ~/cvsstuff
 cvs checkout partiview              # get a new local sandbox to work in, or

 cvs -n -q update partiview          # check if others had made any changes
 cvs update partiview                # if so, update your sandbox and/or resolve conflicts

 cd partiview/src
 ./configure
 emacs partibrains.c                 # edit some files
 make all                            # compile the program
 ./partiview                         # test the program
 emacs partipanel.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
 cd ../..

 cvs release partiview               # if you want to release and remove this sandbox
</PRE>
<HR>
</CODE></BLOCKQUOTE>
<P>
<HR>
<A HREF="partiview-2.html">Next</A>
Previous
<A HREF="partiview.html#toc1">Contents</A>
</BODY>
</HTML>