projects</a>: This Makefile is targeted at applications which
are written to simply try something, or prove an
assumption. Such applications are the
- <a href="../tutorial/chapter-2.step-by-step/index.html" target="_top">step-by-step
+ <a href="../doxygen/tutorial/index.html" target="_top">step-by-step
examples</a>. These small problems are probably not the
usual case in real life, but you may want to take a look at
this file in order to get an idea on how it works, or you
<p>
In addition to the API documentation, we maintain a series of
- <a href="../tutorial/chapter-2.step-by-step/index.html" target="_top">
+ <a href="../doxygen/tutorial/index.html" target="_top">
well-documented example programs</a>, which also follow a certain
``literate programming'' style in that the explanations of what
is happening are integrated into the program source by means of
<h3>Tutorials</h3>
<p>
- The <a href="tutorial/chapter-2.step-by-step/index.html"
+ The <a href="doxygen/tutorial/index.html"
target="_top">tutorial</a> is
for new users of the library. It explains the basic elements of
finite element programs based on the library, and provides small
$D/lac/include/*/*.h \
$D/deal.II/include/*/*.h \
headers/*.h \
- tutorial/doxygen/*.h
+ $(shell ls tutorial/doxygen/)
@echo "=== Generating reference documentation. " \
"This can take several minutes..."
@DOXYGEN@ deal.dox > doxygen.log
* in). It consists of a collection of small programs, each more or
* less built atop of the previous ones, which demonstrate various
* aspects of the library. A more detailed overview can be found <a
- * href="../../tutorial/chapter-2.step-by-step/index.html">on this
+ * href="../tutorial/index.html">on this
* page</a> that also includes short summaries of what each of the
* tutorial programs are supposed to demonstrate.
*
# The IMAGE_PATH tag can be used to specify one or more files or
# directories that contain image that are included in the documentation (see
-# the \image command).
-
-IMAGE_PATH = . \
- ../tutorial/chapter-2.step-by-step/step-1.data \
- ../tutorial/chapter-2.step-by-step/step-2.data \
- ../tutorial/chapter-2.step-by-step/step-3.data \
- ../tutorial/chapter-2.step-by-step/step-4.data \
- ../tutorial/chapter-2.step-by-step/step-5.data \
- ../tutorial/chapter-2.step-by-step/step-6.data \
- ../tutorial/chapter-2.step-by-step/step-7.data \
- ../tutorial/chapter-2.step-by-step/step-8.data \
- ../tutorial/chapter-2.step-by-step/step-9.data \
- ../tutorial/chapter-2.step-by-step/step-10.data \
- ../tutorial/chapter-2.step-by-step/step-11.data \
- ../tutorial/chapter-2.step-by-step/step-12.data \
- ../tutorial/chapter-2.step-by-step/step-13.data \
- ../tutorial/chapter-2.step-by-step/step-14.data \
- ../tutorial/chapter-2.step-by-step/step-15.data \
- ../tutorial/chapter-2.step-by-step/step-16.data \
- ../tutorial/chapter-2.step-by-step/step-17.data \
- ../tutorial/chapter-2.step-by-step/step-18.data \
- ../tutorial/chapter-2.step-by-step/step-19.data \
- ../tutorial/chapter-2.step-by-step/step-20.data \
- ../tutorial/chapter-2.step-by-step/step-21.data \
+# the \image command). This is overwritten in deal.dox
+IMAGE_PATH =
# The INPUT_FILTER tag can be used to specify a program that doxygen should
# invoke to filter for each input file. Doxygen will invoke the filter program
There is no general rule on how to attack implementing a program to
solve your particular problem. However, the way most often taken is
to look at one of the
- <a href="tutorial/chapter-2.step-by-step/index.html"
+ <a href="doxygen/tutorial/index.html"
target="_top">example programs from the tutorial</a> and modify it
such that it solves your equation. This way, a number of problems
can be solved at relatively small effort.
<hr>
<p>
- <a href="tutorial/chapter-2.step-by-step/index.html" target="_top">Tutorial</a><br />
+ <a href="doxygen/tutorial/index.html" target="_top">Tutorial</a><br />
<a href="doxygen/deal.II/index.html" target="_top">Manual</a><br />
</p>