--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"
+ "http://www.w3.org/TR/REC-html40/strict.dtd">
+<html>
+ <head>
+ <link href="screen.css" rel="StyleSheet" title="deal.II Homepage" media="screen">
+ <link href="print.css" rel="StyleSheet" title="deal.II Homepage" media="print">
+ <title>The deal.II FAQ</title>
+ <meta name="author" content="The deal.II authors <deal@iwr.uni-heidelberg.de>">
+ <meta name="keywords" content="deal.II">
+ </head>
+<body>
+
+ <h1>The <acronym>deal.II</acronym> FAQ</h1>
+
+ <ol>
+ <li> <a href="#compiler">How do I change the compiler?</a>
+ <li> <a href="#triangles">Can I use/implement triangles/tetrahedra in <acronym>deal.II</acronym>?</a>
+ </ol>
+
+ <h4><a name="#compiler"></a>How do I change the compiler?</h4>
+
+ See the <a href="http:readme.html#choose-compiler">according
+ section</a> in the <a href="http:readme.html">readme file</a>
+
+ <h4><a name="#triangles"></a>Can I use/implement
+ triangles/tetrahedra in <acronym>deal.II</acronym>?</h4>
+
+ No, you cannot do either. The basic data structures are too much
+ tailored to quadrilaterals and hexahedra. Implementing other cells
+ amounts to re-implementing nearly all grid and DoF classes from
+ scratch.
+
+</body>
+</html>
\ No newline at end of file
<ul>
<li> <a href="#prerequisites">System requirements</a>
<li> <a href="#installation">Installation</a>
- <li> <a href="#compiler">Compiler flags</a>
+ <li> <a href="#compiler-flags">Compiler flags</a>
<li> <a href="#external-libs">Using third-party libraries and
subroutines</a>
<li> <a href="#problems">Problems, questions, mailing lists</a>
</code></pre>
which sets some paths and finds out what compiler you
use. ./configure supports several flags which are discussed
- further down <a href="#options">below</a>.
+ further down <a href="#configuration-options">below</a>.
<p>
</p>
- <a name="options">
+ <a name="configuration-options"></a>
<h3>Configuration options</h3>
+ <a name="choose-compiler"></a>
+ <h4>Changing the compiler</h4>
+
+ If <code>configure</code> uses a wrong compiler, there are two
+ options: first, you can prepend your search path by the directory
+ of the desired compiler. If you do not want to do this (and there
+ are reasons), try the following: If your full compiler paths are
+ <tt>mycc</tt> and <tt>myc++</tt> for your C and C++ compilers,
+ respectively, type into your <tt>csh</tt>:
+ <pre>
+ setenv CC mycc
+ setenv CXX myc++
+ ./configure
+ </pre>
+ or into your <tt>bash</tt>
+ <pre>
+ export CC=mycc
+ export CXX=myc++
+ ./configure
+ </pre>
+
+ <h4>Selecting optional behavior</h4>
You can give several flags to ./configure:
<ul>
<li>
- <a name="compiler">
- <h2>Compiler flags</h2>
+ <a name="compiler-flags">
+ <h4>Compiler flags</h4>
<p>
Since the ISO C++ standard is still quite new and compilers still
enables programs to use interprocess communication and many
other related services using a platform independent
interface. On how to enable using this library, see the section on
- <a href="#options">Configuration Options</a> above.
+ <a href="#configuration-options">Configuration Options</a> above.
</p>
<li>