proposal for common configuration elements for ITAPS services

[Tim Tautges]

This won't work for MOAB; MOAB has both an imesh and an igeom implementation, and there are (many) times when you only 
want imesh, and not igeom.  So, we need them individually controllable.

- tim

On 09/21/2010 11:10 AM, Mark Miller wrote:
>
> On Mon, 2010-09-20 at 21:18 -0700, seol at scorec.rpi.edu wrote:
>
>> Instead of individual option for each implementation (imesh, igeom, irel, etc), how about --enable-itaps for all.
>> In case of imeshp, having both --enable-itaps and --with-mpi (or CC=mpicc) would be interpreted as imeshp enabled.
>>
>
> You know, this sure would be a lot simpler than having to remember
> several different switches. So, to paraphrase your proposal, given a
> product like FOOBAR which implements SOME of the ITAPS interfaces,
> --enable-itaps means to enable all the interfaces FOOBAR implements.
> Optionally, a product could also offer --enable-<some specific ITAPS
> interface>  but that would NOT be required by 'ITAPS-compliant' software.
> ITAPS-compliance means only that --enable-itaps is an available
> configuration switch.
>
> I kinda like this idea.
>
> Mark
>
>
>

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
          phone: (608) 263-8485      1500 Engineering Dr.
            fax: (608) 263-4499      Madison, WI 53706