proposal for common configuration elements for ITAPS services

[Carl Ollivier-Gooch]

So returning to this subject (as per Karen's request), I have two 
suggestions:

1.  For -implementations-, which need to know at configure time whether 
to build support for an interface, I propose we use:

   --enable-imesh
   --enable-imeshp
   --enable-igeom
   --enable-irel
   --enable-ifield

Currently: of four implementations, we have --enable-imesh, 
--enable-iMesh, --enable-itaps, --enable-tsttm (the ref implementation 
needs no flag here, for obvious reasons).  Lower case seems preferred 
(and is typical for configure options).  And imesh is definitely the 
right thing to append (he says, despite currently using something else). 
  Unless someone has strenuous objections, we should standardize to 
this, ideally before the next buildapolooza in a week and a half.

2.  For services and applications, which "only" need to know where to 
find some include and link info, I find Jason's argument in favor of 
using autoconf environment variables compelling, especially the part 
about being able to build multiple components more easily.  What do 
other people think about adopting this as a standard for all our services?

Carl

-- 
------------------------------------------------------------------------
Dr. Carl Ollivier-Gooch, P.Eng.                   Voice: +1-604-822-1854
Professor                                           Fax: +1-604-822-2403
Department of Mechanical Engineering             email: cfog at mech.ubc.ca
University of British Columbia              http://www.mech.ubc.ca/~cfog
Vancouver, BC  V6T 1Z4                  http://tetra.mech.ubc.ca/ANSLab/
------------------------------------------------------------------------