X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=doclib%2FMainpage.dox;h=7a73b31cebdfb5058e9b0a3a7de90f7e9799fef9;hb=0fb5ed1adf2f67dbf47fdfed3f3c8be989cf3618;hp=d7c891e92e6aa754f23d21ac6e4cd5acf5e73474;hpb=61e1b171e37d8e8bac8192d23ed062a1dcae4b80;p=senf.git

diff --git a/doclib/Mainpage.dox b/doclib/Mainpage.dox
index d7c891e..7a73b31 100644
--- a/doclib/Mainpage.dox
+++ b/doclib/Mainpage.dox
@@ -50,8 +50,8 @@
 
     \section senfutil_overview Building Projects using SENF
 
-    When building projects using senf, SENFSCons has a very simple helper module \ref senfutil to
-    make the building of libraries utilizing senf simpler.
+    When building projects using %senf, SENFSCons has a very simple helper module 
+    \ref senf_senfutil "senfutil.py" to make the building of libraries utilizing %senf simpler.
 
     \see \ref senf_senfutil
 */
@@ -227,10 +227,10 @@
 
     The \c senfutil.Doxygen utility autogenerates a \c Doxyfile.
 
-    The utility will search for a SENF documentation in the \c senfdoc and \c senf subdirectories as
-    well as via the senfutil module directory and some other standard locations. If SENF
-    documentation is found, the SENF tagfiles will automatically be added. Links will be resolved to
-    the documentation found.
+    The utility will search for a SENF documentation in the \c senfdoc and \c %senf subdirectories 
+    as well as via the senfutil module directory and some other standard locations. If SENF
+    documentation is found, the SENF tagfiles will automatically be added. Links will be resolved 
+    to the documentation found.
 
     \c senfutil.Doxygen takes some additional optional keyword arguments:
     \li \c doxyheader: Path of an alternative HTML header
@@ -281,7 +281,6 @@
     \li The \c xsltproc XSLT processor (http://xmlsoft.org/XSLT/xsltproc2.html)
     \li The \c graphviz library (http://www.graphviz.org)
 
-
     The library is only tested with gcc-3.4 and 4.0 on Linux. On other POSIX platforms with a BSD
     Socket API, the library should be usable, possibly with some tweaking (except for the Scheduler,
     which relies on \c epoll)
@@ -333,11 +332,11 @@
     $ scons all_tests
     </pre>
 
-    in the \c senf directory. This assumes, that you want to build the library with your default gcc
-    and requires the boost libraries to be available in the system include paths. If this is not the
-    case, you can take a look at <tt>SConfig.template</tt> file. Copy this file to <tt>SConfig</tt>
-    and comment out all the variables you don't want to change (The \e values in the template file
-    are just arbitrary examples).
+    in the \c %senf directory. This assumes, that you want to build the library with your default
+    gcc and requires the boost libraries to be available in the system include paths. If this is 
+    not the case, you can take a look at <tt>SConfig.template</tt> file. Copy this file to
+    <tt>SConfig</tt> and comment out all the variables you don't want to change (The \e values in
+    the template file are just arbitrary examples).
  */
 
 /** \page senf_setup Setting up a new project using SENF