Rationale:
  Treat 3rd-party mpi libraries like any other 3rd-party library. They
  are normally available without debugging and don't know anything
  about the OpenFOAM DP/SP (double/single precision) concept.

We should assume that they've been compiled with the current OpenFOAM
compiler settings and may have compiler-specific runtime requirements.

old: $WM_THIRD_PARTY_DIR/<packageName>/platforms/$WM_ARCH*
new: $WM_THIRD_PARTY_DIR/platforms/$WM_ARCH*/<packageName>

This streamlines the creation of binary packs, eases distribution and
helps when testing the robustness of relocatable installations.

editing the respective settings files.

- foamEtcFile is used to find the files, thus follows the standard
  ~OpenFOAM/fileName expansion mechanism.

- the 'make install' target from ParaView now installs all of the
  includes necessary for compiling plugins.

ENH: move plugin to paraview-$ParaView_MAJOR

It uses mpicc to find out where the installed libraries are.

ENH: upgrade to env. variable to ensight9 (current version)

- foamApps  == app
- foamSol   == sol
- foamTuts  == tut
- foamUtils == util

- removed globalPointPatch*
- removed pointPatchInterpolate*
since all is now inside volPointInterpolation.

leading text

* Something like ParaView_MAJOR=ParaView_3.6 would have previously
  been possible, but this violates paraview's expectation of having
  "lib/paraview-<digits>.<digits>"

* TODO? If desired, the ParaView_MAJOR could be determined
  automatically in the script.

  For example,
      ParaView_MAJOR=`echo $ParaView_VERSION | \
          sed -e 's/^\([0-9][0-9]*\.[0-9][0-9]*\).*$/\1/'`

  Or even,
      ParaView_MAJOR=${ParaView_VERSION%.[0-9]}

  Except that the second version fails if the minor version reaches
  double digits.

- moved to $FOAM_LIBBIN/paraview so that built libraries sit in their
  own folder - avoids PV error msgs on start-up when it tries to load
  all libs under the $PV_PLUGIN_PATH

According to the openmpi release information:
- Use GNU Libtool 2.2.6b to build Open MPI, which updates the
  embedded "libltdl" library to fix a potential security
  vulnerability. There are no other changes compared to Open MPI
  v1.3.4.

For development purposes it should thus be adequate to simply

    ( cd $WM_THIRD_PARTY_DIR && mv openmpi-1.3.4 openmpi-1.4 )

if you don't wish to recompile things.

According to the openmpi release information:
- Use GNU Libtool 2.2.6b to build Open MPI, which updates the
  embedded "libltdl" library to fix a potential security
  vulnerability. There are no other changes compared to Open MPI
  v1.3.4.

For development purposes it should thus be adequate to simply

    ( cd $WM_THIRD_PARTY_DIR && mv openmpi-1.3.4 openmpi-1.4 )

if you don't wish to recompile things.

- exception calcType.H since it'll most likely be used for building
  applications anyhow

- use quailified names in more of the lagrangian code

- killed some tab indents in various places.