Re: [ccmtools-devel] Local and remote tests

[Teiniker E. <ego...@tu...>]

Hi Leif!

Quoting Leif Johnson <le...@am...>:

> On Tue, 18 Nov 2003, Egon Teiniker wrote:
> > I have implemented some _check_*_remote.cc files that test the
> > generated remote components. I'm not sure if I should put these files
> > into the test/CppGenerator/*/CCM_Test directories or use a separate
> > test/CppRemoteGenerator tree - what do you think about that?
>
> Why don't we create the remote environment when we create the local
> environment, and get rid of the ccmtools-c++remote-* scripts ? We can
> add a switch to the ccmtools-c++-{environment|generate} scripts to do
> the remote environment, components and tests. There's already a switch
> in there for the Python wrappers ; it just isn't used at the moment.
> Comments ?

I think that installing and using the local components is much easier (no CORBA)
that handling remote components. Thus, local components can be the gateway drug
to CCM ;-) After that the remote stuff is just another step...

So I think that we should separate the following use cases:
a) Local component development (C++, Confix)
b) Local and remote component development (C++, Confix, Mico)

:-) Egon