On Sep 4, 2007, at 1:33 PM, Ethan Mallove wrote:
So if I have the following line in my [Test build: intel]
section, MTT will now build and run the Intel tests *twice*?
Once with compiler-A and once with compiler-B?
setenv = ("/path/to/compiler-A", "/path/to/compiler-B")
setenv is a bad
On Tue, Sep/04/2007 12:47:29PM, Jeff Squyres wrote:
> On Sep 4, 2007, at 10:57 AM, Ethan Mallove wrote:
>
> > So if I have the following line in my [Test build: intel]
> > section, MTT will now build and run the Intel tests *twice*?
> > Once with compiler-A and once with compiler-B?
> >
> >
On Sep 4, 2007, at 10:57 AM, Ethan Mallove wrote:
So if I have the following line in my [Test build: intel]
section, MTT will now build and run the Intel tests *twice*?
Once with compiler-A and once with compiler-B?
setenv = ("/path/to/compiler-A", "/path/to/compiler-B")
setenv is a bad
So if I have the following line in my [Test build: intel]
section, MTT will now build and run the Intel tests *twice*?
Once with compiler-A and once with compiler-B?
setenv = ("/path/to/compiler-A", "/path/to/compiler-B")
-Ethan
On Tue, Sep/04/2007 10:03:09AM, Jeff Squyres wrote:
> I think
So we will get a multiplicative effect on the following INI
parameters?
* setenv
* unsetenv
* env_module
Any other parameters?
-Ethan
On Fri, Aug/31/2007 10:18:30PM, MTT wrote:
> #245: Support multiplicative effect for other INI params
>
