readme

Delaunay三角形的网格剖分程序

THIS DOC IS PRELIMINARY!!!

The make mechanism finally is in a state where we can explain what we are
doing here...

Some explanations why we proceed as we do:

1) We use the lcd of all Makefile syntaxes (i.e. no VPATH, no if etc), 
   we don't want do depend on gmake etc.
2) As we understand, the autoconf stuff detects the wrong data for us. We try
   to have reasonably clean ANSI C so it is not that important if bcopy is there.
3) Binaries and libraries  
   for multiple architectures should coexist in the same directory tree.
############################################################################
<config>.mk

The following flags need to be set (for examples, please see the actual files)

arch_ldflags: can contain special locations of certain system libs etc.
              mostly empty
arch_shldflags: flags to define how to make a shared library
              mostly quite difficult to detect, therefore not used in 
             the default installations


arch_cc: which C compiler to use
        mostly cc
arch_cflags: cflags  etc.
        mostly -g -O etc.
    
  Here, you should tell us  how the fortran compiler generates external names to be called from C:
  -DFORTRAN   : CALL FOO(BAR) -> FOO(bar);
  -DFORTRAN_  : CALL FOO(BAR) -> FOO_(bar);
  -Dfortran   : CALL FOO(BAR) -> foo(bar);
  -Dfortran_  : CALL FOO(BAR) -> foo_(bar); (default)
  (these options cannot be combined)


arch_cxx: which C++ compiler to use
          mostly  CC

arch_cxxflags: C++ compiler flags
        mostly -g -O  -blablablaHowToMakeTemplates


arch_fc: which fortran compiler to use. Currently all fortran in pdelib 
         is f77
        mostly f77

arch_fflags: Fortran compiler flags
        mostly -g -O etc.


arch_fortlibs: fortran runtime libraries (use when linking fortran code with ld
               and without fortran driver)
        can be detected with something like f77 -v HelloWorld.f

System libraries:
arch_termcap: the termcap library (used to link with readline). This is 
              actually detected by the readline config, but until now,
              we have no mechanism to read out this info.

arch_blas: the blas library 
arch_lapack: the lapack library
arch_grlibs: OpenGL and X11 libraries 
arch_libs: other necessary libs (as -ldl)
              
arch_ranlib: the ranlib command. Most ar commands don't need this,
             mostly true


############################################################################
# head.mk:
#
# Define pdelib dependent part of make variables from PDELIB_HOME, 
# PDELIB_CONFIG and the arch_*flags from $(PDELIB_CONFIG).mk
# 
#
# This file does not contain targets and should not crash 
#  without PDELIB_CONFIG set
#
# All of the variables with capital letters are used by User makefiles and default rules.
# They can be overwritten. To avoid recursive variable definitions, eg. for appending
# values, the variables with lower case names can be used to get the actual value
 of the variable
!!! example here!!!

#
# To "attach" an installed pdelib, the user can include this file
# and define his own variables using pdelib data. A convenient base for
 cloning is the UserMakefile in the top level directory


You can access the following make variables:
...



##################################################################
# foot.mk
# In this file, all the usual default make rules are overwritten
# using the pdelib make variables, defined in head.mk. 
# .c.o uses PDELIB_CC, PDELIB_CFLAGS etc.
# This avoids conflicts with user defined makefiles.
#