From 61e4c1ca775ba11bf400cc08adaaa608e19a680a Mon Sep 17 00:00:00 2001
From: maier ',\
- '$$($1)
$($1) ')
-
-VARIABLE_VALUES = $(foreach v,$(VARIABLES),$(call expand_variable,$v))
-
-makefiles.html: Makefile makefiles.1.html $D/common/Make.global_options makefiles.2.html
- @cat makefiles.1.html > $@
- @echo "" >> $@
- @echo "
" >> $@
- @echo "Makefile variable Value in common/Make.global_options
" >> $@
- @echo $(VARIABLE_VALUES) >> $@
- @echo "
\n"; - -while (<>) { - # ignore subversion tag - next if m!^#\*\s*\$Id:!; - - # substitute special characters - s/&/&/g; - s/</g; - s/>/>/g; - s/\t/ /g; - - if (($state == $program_mode) && m!^\s*#!) - { - $state = $comment_mode; - print "\n"; - print "\n"; - print "
\n"; - } - # if in comment mode and no comment line: toggle state. - # don't do so, if only a blank line - elsif (($state == $comment_mode) && !m!^\s*#! && !m!^\s*$!) - { - $state = $program_mode; - print "
\n"; - print "\n"; - print "\n";
- }
-
- if ($state == $comment_mode)
- {
- m!\s*#\s*(.*)!;
- print $1, "\n";
- print "\n\n" if $1 =~ m!^\s*$!;
- }
- else
- {
- print " $_";
- }
-}
-
-if ($state == $program_mode) {
- print "
\n";
-}
-
-print "\n\n";
diff --git a/deal.II/doc/development/makefiles.1.html b/deal.II/doc/development/makefiles.1.html
deleted file mode 100644
index cbf3d19d40..0000000000
--- a/deal.II/doc/development/makefiles.1.html
+++ /dev/null
@@ -1,387 +0,0 @@
-
-
-
-
-
- The file common/Make.global_options
exports several
- make variables to other Makefiles which
- include it. You will want to include this file into the Makefiles of
- your project to use the same compiler flags and to access the paths
- to libraries. This page documents available
- variables, documents the values which are used
- in your local installation, and shows
- generic Makefiles which you may want to use
- in your own projects.
-
- Following is a partial list of available variables which are exported to
- other Makefiles. There are additional variables, in particular ones that
- determine the interaction with other libraries such as PETSc, Trilinos,
- METIS, etc; for details on these variables, take a look
- at common/Make.global_options
.
-
D
- Path to the deal.II library -
-CXX
- Executable name of the C++ compiler -
-CC
- Executable name of the C compiler, which - is used to generate shared libraries -
-GXX-VERSION
- Name and version of the C++ compiler. Possible
- names presently include
- gcc3.3
, gcc3.4
,
- gcc4.0
, gcc4.1
, etc,
- ibm_xlc
, MIPSpro
,
- sun_workshop
, sun_forte
,
- intel_icc5
, intel_icc6
,
- intel_icc7
, compaq_cxx
, and
- probably a few more as well. Not all of
- these compilers are actually supported (see the
- ReadMe file for a
- list of supported compilers and platforms), it is only a list of
- recognized compilers.
- Note that the naming of this variable is historical (it
- should read CXX-VERSION
), since
- it is also used even if the compiler is not the GNU C++
- compiler.
-
GXX-VERSION-DETAILED
- Like GXX-VERSION, just that it may also contain the dot version - number, for example gcc3.3.3. -
-CC-VERSION
- Name and version of the CC compiler. Possible names are - similar to the ones listed above. -
-F77
- Executable name of the F77 compiler; often, no Fortran - compiler is needed, in which case the variable may be empty if - none was found -
-F77-VERSION
- Name and version of the Fortran 77 compiler. Possible
- names presently include egcs1.1
,
- gcc2.95
, gcc2.96
,
- gcc2.97
, gcc3.0
, SunF77
,
- AIXF77
, MIPSproF77
;
- there may be others in the future, if we have access to
- other systems
-
SHLIBLD
- Executable name of compiler that is used to link object - files to shared libraries. This will usually be the C++ - compiler. -
-enable-shared
- Determines whether shared or static libraries are used.
- In the former case it is set to yes
.
-
enable-threads
- Determines whether multiple threads should be used or not.
- In the former case it is set to yes
.
-
PERL
- Executable name of the `perl' program -
-DEAL_II_MAJOR
- Major version number of the deal.II - library, i.e. the number before the first dot. Note that - this version number is also available in programs through a - preprocessor variable -
-DEAL_II_MINOR
- Minor version number of the deal.II - library, i.e. the number after the first dot; if there are - further numbers, like in version 3.0.1, then they are - discarded as these versions only fix bugs but do not change - features. Note that this version number is also available - in programs through a preprocessor variable -
-TARGET
- The target triplet as returned by config.guess. For example, on the - system where I write this, it is i686-pc-linux-gnu, but it may also - be sparc-sun-solaris2.7, or whatever config.guess determines for - your system. -
-LIBDIR
- Path to the deal.II libraries. -
-LIBPATH
- All the library paths (the deal.II libraries as well as other - libraries we need to link with) prefixed by -L, i.e. the - flags needed by the compiler to find the libraries - when they are linked in. These -L paths are appended to what - was in $(LIBPATH) before. -
-LIBS
- Additional libraries to be linked in, such as Fortran - support, or Tecplot libraries when binary output is available. -
-F77LIBS
- Libraries to be linked in when we link with Fortran
- files. These libraries are checked at configuration time,
- and are included into $(LIBS)
when they are
- actually needed
-
OBJEXT
- Extension of object files. On unix, this is usually simply
- o
, on Windows systems it is obj
.
-
EXEEXT
- Extension of executables. On unix, this is usually the
- empty string, on Windows systems it is .exe
.
-
static-lib-suffix
- File extension of static libraries. Usually set to .a -
-shared-lib-suffix
- File extension of shared libraries. If shared libraries
- are supported, this suffix is usually .so
on unix-like
- systems, but is .dylib
on Mac OS X
- and .dll
on windows.
-
lib-suffix
- File extension of libraries. Depending on the value of
- enable-shared
, it is either set to
- static-lib-suffix
or to
- shared-lib-suffix
.
-
lib-deal2.o lib-deal2.g
- Path and filename of the deal.II libraries. -
-INCLUDE
All include paths figured out by the configure
- script are now included into the variable
- $(INCLUDE)
(which include the compiler option
- -I in front of each directory). They are also
- automatically included in your compiler calls as soon as you use
- $(CXXFLAGS.g)
or $(CXXFLAGS.o)
.
-
An exception to this rule are paths listed below. These are
- added to the variable $(INCLUDE)
only during make.
-
include-path-contrib-petsc
- include-path-contrib-petsc-bmake
-
- If PETSc is used, then these variables have the paths to the usual - PETSc include files and the PETSc architecture dependent include - files. - (See the - ReadMe - file for more information on installation of PETSC.) -
-include-path-contrib-metis
-
- If METIS is used, then this variable has the path to the METIS - include files. (See the - ReadMe - file for more information on installation of METIS.) -
-CXXFLAGS.g
- C++ compiler flags for debug mode -
-CXXFLAGS.o
- C++ compiler flags for optimized mode -
-CCFLAGS.g
- C compiler flags for debug mode. -
-CCFLAGS.o
- C compiler flags for optimized mode. -
-F77FLAGS.g
- Fortran 77 compiler flags for debug mode -
-F77FLAGS.o
- Fortran 77 compiler flags for optimized mode -
-LDFLAGS
- General linker flags -
-common/Make.global_options
:
-
-
diff --git a/deal.II/doc/development/makefiles.2.html b/deal.II/doc/development/makefiles.2.html
deleted file mode 100644
index 77e0eae366..0000000000
--- a/deal.II/doc/development/makefiles.2.html
+++ /dev/null
@@ -1,91 +0,0 @@
-
-
- - deal.II comes with sample Makefiles for - applications that use this library. They show how to use the information - provided by the variables explained above. -
- -- At present, there are two such Makefile templates. All Makefiles - need slight modifications before they will work in your - project; the places for modifications are marked and easy to find. The - templates are: - -
- Small
- project Makefile: This Makefile is targeted at small
- applications consisting of only a single .cc
- file. Examples of this kind are the
- step-by-step
- tutorial programs.
- You can find this Makefile
- here.
-
- Large
- projects: This file is targeted at larger projects, and
- for this file to work, we already assume a certain
- subdirectory structure of your project. In particular, it
- assumes that in your project directory the following
- subdirectories exist (where project
is the
- directory in which the whole project is located):
-
project/source
: The location of all
- your .cc
files.
- project/include
: The location of all
- your .h
files.
- project/lib
: Where the Makefile will
- put the final executable.
- project/lib/1d
: Where the Makefile will
- put your object files if you compile for 1d.
- project/lib/2d
: Same for 2d.
- project/lib/3d
: Same for 3d.
- - Using this - directory structure, it is possible to quickly switch - between dimensions in which a program shall run in, - enabling us to develop applications which run in 1d, 2d, or - 3d without long compilation times. Furthermore, placing - object files in different directories prevents cluttering - directories with unnecessarily many files. -
- -
- The dimension for which the project shall be compiled is
- not stated in the source code, as in the small projects
- Makefile, but is determined by a flag set in the
- Makefile. The Makefile then makes sure that the preprocessor
- constant deal_II_dimension
is set appropriately and
- passed through to the compiler when creating object files.
-
- You can find this Makefile - here. -
-$MSGGMTDATE(CUR;%Y - %b - %d)$
-
-$FROMNAME$ ($FROMADDRNAME$ at $FROMADDRDOMAIN$)
-
-$GMTDATE$