<commit_before><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
	  "http://www.w3.org/TR/html4/loose.dtd">
<html>
  <head>
    <title>The deal.II Readme</title>
    <link href="screen.css" rel="StyleSheet">
    <meta name="author" content="the deal.II authors <authors @ deal<EMAIL>>">
    <meta name="copyright" content="Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 by the deal.II authors">
    <meta name="date" content="$Date$">
    <meta name="svn_id" content="$Id$">
    <meta name="keywords" content="deal.II">
  </head>

  <body>


    <h1>Installation instructions and further information
      on <acronym>deal.II</acronym> </h1>

    <table class="tutorial" width="60%">
      <tr><th colspan="2"><b><small>Table of contents</small></b></th></tr>
      <tr><td valign="top">
	  <ul>
	    <li> <a href="#prerequisites">System requirements</a>
	      <ul>
		<li> <a href="#supported">Supported platforms</a>
		<li> <a href="#additional-software">Additional software requirements</a>
	      </ul>
	    <li> <a href="#installation">Installation</a>
	      <ul>
		<li>  <a href="#unpacking">Unpacking</a>
		<li>  <a href="#configuration">Configuring and building the library</a>
		<li>  <a href="#configuration-options">Configuration options</a>
		  <ul>
		    <li> <a href="#optional">Selecting optional behavior</a>
		    <li> <a href="#optional-software">Optional interfaces to
			other software packages</a>
		    <li> <a href="#conf-details">More information on configuring
			and building the library</a>
		  </ul>
	      </ul>
	    <li> <a href="#problems">Problems, questions, mailing lists</a>
	    <li> <a href="#license">License</a>
	  </ul>
	</td>
      </tr>
    </table>


    <a name="prerequisites"></a>
    <h2>System requirements</h2>

    <a name="supported"></a>
    <h3>Supported platforms</h3>

    <p>
      <acronym>deal.II</acronym> is mostly developed on Linux using the
      <a href="http://gcc.gnu.org">GCC</a> compiler. However, it is not
      platform specific and we strive to keep the source code C++
      standard compliant.
    </p>

    <p>
      We expect that <acronym>deal.II</acronym> should work on the following
      platforms:
      <ul>
	<li>Linux: using the GCC compiler versions 4.0 or later; using the
	  clang compiler version 3.1 or later.
	<li>Mac OS X: using the GCC compiler version 4.0 or later (Please see
          the <a href="http://dealii.sourceforge.net/index.php?title=Main_Page"
		 target="_top">deal.II Wiki</a> for installation issues);
	<li><a href="http://www.cygwin.com"
               target="_top">Cygwin/Windows</a> with recent GCC
          versions. For <a href="http://dealii.sourceforge.net/index.php?title=Windows"
			   target="_top">installing on Windows</a>, please refer to
          additional information on
          the <a href="http://dealii.sourceforge.net/index.php?title=Main_Page"
		 target="_top">deal.II Wiki</a>!
      </ul>
      Most other combinations of POSIX-style operating systems and C++
      standards compliant compilers should also work. If they don't, please
      report it as a bug.
    </p>

    <p>
      There are many C++ compilers out there. Our experience is that,
      unfortunately, most of them do not fully support the C++ 1998 standard
      upon which we build, and they eventually fail on a project as large as
      deal.II. Your best bet is to stick with the ones listed above. The only
      platform where this is not trivial is Microsoft Windows where the widely
      used Microsoft Visual C++ compiler simply has too many bugs supporting
      advanced C++ code.
    </p>


    <a name="additional-software"></a>
    <h3>Additional software requirements</h3>

    In order to compile and use the <acronym>deal.II</acronym>
    libraries you need to have the following programs installed:
    <ul>
      <li> <p>
          <a href="http://www.gnu.org/software/make/" target="_top">GNU make</a>, version
          3.78 or later. Non-GNU versions of this program will usually fail
          to work and are not supported.
	</p>

      <li> <p>
          <a href="http://www.cmake.org/" target="_top">CMake</a> version 2.8.8 or later.
	</p>

      <li> <p>
          <a href="http://www.perl.org/" target="_top">Perl 5.x</a>.
	</p>

      <li> <p>
          For debugging programs, we have found that the
	  <a href="http://www.gnu.org/software/gdb/" target="_top">GNU
	    debugger GDB</a> is an invaluable tool. GDB is a text-based tool
	    not always easy to use; <a href="http://www.kdbg.org/"
	    target="_top">kdbg</a>, is one of many graphical user interfaces
	    for it. Most integrated development environments
	    like <a href="http://www.kdevelop.org/" target="_top">kdevelop</a>
	    or <a href="http://eclipse.org/" target="_top">Eclipse</a> have built
	    in debuggers as well.
	</p>

      <li> <p>
          To generate the documentation locally on your
	  machine from the <acronym>deal.II</acronym> header files, you need
	  <a href="http://www.doxygen.org/" target="_top">doxygen</a>
	  on your machine. If not, you can still work with the library and
	  use the documentation provided on our homepage for reference.
          In order to generate inheritance graphs for classes, doxygen
          can use the <code>dot</code> program, which is part of the
	  <a href="http://www.graphviz.org" target="_top">GraphViz</a>
          package. If this program is not available, then doxygen attempts to
          generate text-mode graphs; these are much less nice, though.
	</p>

      <li> <p>
          The library generates output in formats readable by
          <a href="http://www.ucc.ie/gnuplot/gnuplot-faq.html" target="_top">GNUPLOT</a>,
	  <a href="http://www-xdiv.lanl.gov/XCM/gmv/" target="_top">GMV
 	    (general mesh viewer)</a>,
	  <a href="http://www.amtec.com" target="_top">Tecplot</a> (ASCII and binary),
          <a href="http://public.kitware.com/VTK/"
             target="_top">Visualization Toolkit (Vtk)</a>,
	  <a href="http://www.avs.com" target="_top">AVS Explorer</a>,
	  <a href="http://www.opendx.org" target="_top">Open DX</a>,
	  <a href="http://www.povray.org" target="_top">Povray</a>,
          and directly to Encapsulated Postscript. GNUPLOT and a
          postscript viewer (for EPS) should be available almost
          everywhere. In the last few years, most new visualization
          programs have moved to support VTK/VTU format. There are a
          number of excellent programs that can read VTK and VTU, such as <a
									     href="http://www.llnl.gov/visit/" target="_top">Visit</a>,
	  <a href="http://www.paraview.org/HTML/Index.html"
             target="_top">ParaView</a>, as well as others.
	  Povray is freely available for almost all
          platforms. AVS is a commercial program available for most
          Unix flavors. Tecplot is a commercial program available for
          Windows and most Unix platforms.
	</p>

	<p>
	  In case you didn't find your favorite graphics format above, adding a new
	  writer to <acronym>deal.II</acronym> is not too difficult as only a
	  simple
	  intermediate format needs to be
	  converted into output (without references to cells,
	  nodes, types of finite elements, and the like).
	</p>
    </ul>




    <a name="installation"></a>
    <h2>Installation</h2>

    <a name="unpacking"></a><commit_msg>Some minor changes and reformatting<commit_after><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
	  "http://www.w3.org/TR/html4/loose.dtd">
<html>
  <head>
    <title>The deal.II Readme</title>
    <link href="screen.css" rel="StyleSheet">
    <meta name="author" content="the deal.II authors <authors @ dealii.org>">
    <meta name="copyright" content="Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 by the deal.II authors">
    <meta name="date" content="$Date$">
    <meta name="svn_id" content="$Id$">
    <meta name="keywords" content="deal.II">
  </head>

  <body>


    <h1>Installation instructions and further information
      on <acronym>deal.II</acronym> </h1>

    <table class="tutorial" width="60%">
      <tr><th colspan="2"><b><small>Table of contents</small></b></th></tr>
      <tr><td valign="top">
	  <ul>
	    <li> <a href="#prerequisites">System requirements</a>
	      <ul>
		<li> <a href="#supported">Supported platforms</a>
		<li> <a href="#additional-software">Additional software requirements</a>
	      </ul>
	    <li> <a href="#installation">Installation</a>
	      <ul>
		<li>  <a href="#unpacking">Unpacking</a>
		<li>  <a href="#configuration">Configuring and building the library</a>
		<li>  <a href="#configuration-options">Configuration options</a>
		  <ul>
		    <li> <a href="#optional">Selecting optional behavior</a>
		    <li> <a href="#optional-software">Optional interfaces to
			other software packages</a>
		    <li> <a href="#conf-details">More information on configuring
			and building the library</a>
		  </ul>
	      </ul>
	    <li> <a href="#problems">Problems, questions, mailing lists</a>
	    <li> <a href="#license">License</a>
	  </ul>
	</td>
      </tr>
    </table>


    <a name="prerequisites"></a>
    <h2>System requirements</h2>

    <a name="supported"></a>
    <h3>Supported platforms</h3>

    <p>
      <acronym>deal.II</acronym> is mostly developed on Linux using the
      <a href="http://gcc.gnu.org">GCC</a> compiler. However, it is not
      platform specific and we strive to keep the source code C++
      standard compliant.
    </p>

    <p>
      We expect that <acronym>deal.II</acronym> should work on the following
      platforms:
      <ul>
	<li>Linux: using the GCC compiler versions 4.0 or later; using the
	  Clang compiler version 3.0 or later; using the ICC compiler
          version 12 or later.
	<li>Mac OS X: using the GCC compiler version 4.0 or later (Please see
          the <a href="http://dealii.sourceforge.net/index.php?title=Main_Page"
		 target="_top">deal.II Wiki</a> for installation issues);
	<li><a href="http://www.cygwin.com"
               target="_top">Cygwin/Windows</a> with recent GCC
          versions. For <a href="http://dealii.sourceforge.net/index.php?title=Windows"
			   target="_top">installing on Windows</a>, please refer to
          additional information on
          the <a href="http://dealii.sourceforge.net/index.php?title=Main_Page"
		 target="_top">deal.II Wiki</a>!
      </ul>
      Most other combinations of POSIX-style operating systems and C++
      standards compliant compilers should also work. If they don't, please
      report it as a bug.
    </p>

    <p>
      There are many C++ compilers out there. Our experience is that,
      unfortunately, most of them do not fully support the C++ 1998 standard
      upon which we build, and they eventually fail on a project as large as
      deal.II. Your best bet is to stick with the ones listed above. The only
      platform where this is not trivial is Microsoft Windows where the widely
      used Microsoft Visual C++ compiler simply has too many bugs supporting
      advanced C++ code.
    </p>


    <a name="additional-software"></a>
    <h3>Additional software requirements</h3>

    <p>
      In order to compile and use the <acronym>deal.II</acronym>
      libraries you need to have the following programs installed:
    </p>
    <ul>
      <li> <p>
          <a href="http://www.cmake.org/" target="_top">CMake</a> version 2.8.8 or later
	</p>

      <li> <p>
          <a href="http://www.gnu.org/software/make/" target="_top">GNU make</a>, version
          3.78 or later (or any other generator supported by CMake)
	</p>

      <li> <p>
          For generating the documentation:
          <a href="http://www.perl.org/" target="_top">Perl 5.x</a>,
	  <a href="http://www.doxygen.org/" target="_top">doxygen</a>
          and <code>dot</code>, which is part of the
	  <a href="http://www.graphviz.org" target="_top">GraphViz</a>
          package
	</p>

      <li> <p>
          For debugging programs, we have found that the
	  <a href="http://www.gnu.org/software/gdb/" target="_top">GNU
	    debugger GDB</a> is an invaluable tool. GDB is a text-based tool
	    not always easy to use; <a href="http://www.kdbg.org/"
	    target="_top">kdbg</a>, is one of many graphical user interfaces
	    for it. Most integrated development environments
	    like <a href="http://www.kdevelop.org/" target="_top">kdevelop</a>
	    or <a href="http://eclipse.org/" target="_top">Eclipse</a> have built
	    in debuggers as well.
	</p>

      <li> <p>
          The library generates output in formats readable by
          <a href="http://www.ucc.ie/gnuplot/gnuplot-faq.html" target="_top">GNUPLOT</a>,
	  <a href="http://www-xdiv.lanl.gov/XCM/gmv/" target="_top">GMV
 	    (general mesh viewer)</a>,
	  <a href="http://www.amtec.com" target="_top">Tecplot</a> (ASCII and binary),
          <a href="http://public.kitware.com/VTK/"
             target="_top">Visualization Toolkit (Vtk)</a>,
	  <a href="http://www.avs.com" target="_top">AVS Explorer</a>,
	  <a href="http://www.opendx.org" target="_top">Open DX</a>,
	  <a href="http://www.povray.org" target="_top">Povray</a>,
          and directly to Encapsulated Postscript.
        </p>
        <p>
          <code>gnuplot</code>
          and a postscript viewer (for <code>eps</code>) should be
          available almost everywhere. In the last few years, most
          new visualization programs have moved to support
          <code>vtk</code>/<code>vtu</code> format. There are a number
          of excellent programs that can read <code>vtk</code> and
          <code>vtu</code>, such as
          <a href="http://www.llnl.gov/visit/" target="_top">Visit</a>,
          <a href="http://www.paraview.org/HTML/Index.html" target="_top">ParaView</a>,
	  as well as others. Povray is freely available for almost all
	  platforms. AVS is a commercial program available for most Unix
	  flavors. Tecplot is a commercial program available for Windows
	  and most Unix platforms.
	</p>
	<p>
	  In case you didn't find your favorite graphics format above,
	  adding a new writer to <acronym>deal.II</acronym> is not too
	  difficult, as only a simple intermediate format needs to be
	  converted into output (without references to cells, nodes,
	  types of finite elements, and the like).
	</p>
    </ul>




    <a name="installation"></a>
    <h2>Installation</h2>

    <a name="unpacking"></a>
{'fraction_non_alphanumeric': 0.14165864392793287, 'fraction_numerical': 0.01279053775271627, 'mean_word_length': 2.929478519319103, 'pattern_counts': {'":': 0, '<': 385, '<?xml version=': 0, '>': 385, 'https://': 0, 'lorem ipsum': 0, 'www.': 36, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '735274', 'n_tokens_mistral': 4945, 'n_tokens_neox': 4481, 'n_words': 1449}