proposal for common configuration elements for ITAPS services

[Xiaolin Li]

Please add Yijing Hu to this list. Thanks.

yijinghu.ams at gmail.com

On Fri, 2010-09-10 at 10:08 -0500, Tim Tautges wrote:
> 
> On 09/10/2010 09:54 AM, Carl Ollivier-Gooch wrote:
> > 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?
> >
> 
> That's for autoconf-configured services and apps.  I strongly believe we should also keep the current standard of 
> building a iXxx-Defs.inc containing the make variables IXXX_INCLUDES and IXXX_LIBS.
> 
> - tim
> 
> > Carl
> >
>