web/hosts/www installing.xml,1.10,1.11

Update of /cvs/fresco/web/hosts/www
In directory frida:/tmp/cvs-serv25563

Modified Files:
	installing.xml 
Log Message:
Ben provided me with a patch to the installing file a while back. I finally
managed to check it in... Sorry for the delay, Ben!


Index: installing.xml
===================================================================
RCS file: /cvs/fresco/web/hosts/www/installing.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- installing.xml	12 Feb 2003 03:58:52 -0000	1.10
+++ installing.xml	20 Apr 2004 18:52:15 -0000	1.11
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
 
 <page xmlns:xlink="http://www.w3.org/1999/xlink"
-      title="Installing" id="Running/Installing">
+  title="Installing" id="Running/Installing">
   <left-area>
     <menu xlink:href="menu.xml"/>
   </left-area>
@@ -25,30 +25,37 @@
       There are currently three ways to download Fresco. You can check out the
       sources directly from <link xref="cvs">CVS</link>,
       download a nightly <link xref="snapshots">snapshot</link>,
-      or you can get release <link href="http://sourceforge.net/projects/berlin/">packages</link>.
+      or you can get release
+ <link href="http://sourceforge.net/projects/berlin/">packages</link>.
     </text-body>
     <text-header-small>Configuration</text-header-small>
     <text-body>
-      In case you use the CVS version, you have to step into the toplevel
-      directory ('Fresco'), and call ./autogen.sh, to generate configure
-      scripts and helper files.
+      In case you use the CVS version, you have to step into the top-level
+      source directory ('Fresco'), and call
+      <code-block>
+        <code-item>./autogen.sh</code-item>
+      </code-block>
+
+      to generate configure scripts and helper files.
     </text-body>
     <text-body>
       Decide where to build Fresco, either inside the source tree (let's
-      refer to this as $fresco-src), or (the recomended way), in a separate
+      refer to this as $fresco-src), or (the recommended way), in a separate
       build directory ($fresco-build).
       Step into the build directory, and run configure:
 
       <code-block>
         <code-item>cd $fresco-build</code-item>
-        <code-item>$fresco-src/configure</code-item>
+        <code-item>$fresco-src/configure --prefix=/install/path/</code-item>
       </code-block>
     </text-body>
     <text-body>
       this will set up the build tree and check for the available packages.
     </text-body>
     <text-body>
-      [ Add support for interactive configuration and document the options here]
+       [ Add support for interactive configuration and document the options
+         here. There is a configure for each of Prague, Fresco etc., all
+         invoked by the top-level configure. ]
     </text-body>
     <text-header-small>Building</text-header-small>
     <text-body>
@@ -60,41 +67,58 @@
       	<code-item>make -s</code-item>
       </code-block>
     </text-body>
-    <text-header-small>Testing</text-header-small>
+    <text-header-small>Installing</text-header-small>
     <text-body>
-      you should now find some libraries in $fresco-build/lib, modules in
-      $fresco-build/module, and binaries in $fresco-build/bin. If you want
+      To install Fresco into the path you specified during configure run:
+      <code-block>
+        <code-item>make install</code-item>
+      </code-block>
+    </text-body>
+    <text-header-small>Running</text-header-small>
+    <text-body>
+      You should now find some libraries in $prefix/lib, modules in
+      $prefix/module, and binaries in $prefix/bin. If you want
       to run fresco at this place, you have to tell the loader where to look
       for the libraries, and, in case you use the python environment, tell
       python where to find the fresco modules:
+
       <code-block>
-        <code-item>setenv LD_LIBRARY_PATH $fresco-build/lib:$LD_LIBRARY_PATH</code-item>
-	<code-item>setenv PYTHONPATH $fresco-build/lib/python:$PYTHONPATH</code-item>
+        <code-item>export LD_LIBRARY_PATH $prefix/lib:$LD_LIBRARY_PATH</code-item>
+	<code-item>export PYTHONPATH $prefix/lib/python:$PYTHONPATH</code-item>
       </code-block>
     </text-body>
     <text-body>
       or similar depending on your shell.
-      The fresco server is in $fresco-build/bin/server, and to tell him about
-      the current (temporary) location of the resources (fonts, modules, rasters, ...)
-      you have to provide him with a resource file containing the paths:
+      The fresco server is in $prefix/bin/server. Use
       <code-block>
-        <code-item>bin/server -r config/frescorc</code-item>
+        <code-item>$prefix/bin/server</code-item>
       </code-block>
+      to run it.
     </text-body>
     <text-body>
-      Voila ! That should run the server.
-    </text-body>
-    <text-header-small>Installing</text-header-small>
-    <text-body>
-      Sorry, the install target isn't finished yet, but we are working on it.
+      Voila! That should run the server. You may want to try this:
+      <code-block>
+        <code-item>$prefix/bin/server -e $prefix/bin/fresco-demo</code-item>
+      </code-block>
+      to have a client started and connecting to the server right after
+      the start up of the server.
     </text-body>
+
     <text-header-small>Troubleshooting</text-header-small>
     <text-body>
       There are a couple of places which are frequently subject to problems.
       Please consult the <link xref="faq"/>, and
       please be sure that third party libraries are correctly installed before
-      you post about a bug. For example, the by far most frequent problem encountered
-      is reported by people who forgot to start the name server...
+      you post about a bug. For example, the by far most frequent problem
+      encountered is reported by people who forgot to start the name server...
+      (this shouldn't be a problem any longer!).
+    </text-body>
+    <text-body>
+      Another common problem are missing fonts. The fresco server checks its
+      for true-type and type 1 fonts (and other fonts supported by freetype)
+      in the directories specified in fontpath in $prefix/etc/berlinrc. You
+      may need to adapt this path to match up with your system's font
+      directories.
     </text-body>
     <text-body>
       Good luck,   Stefan