Re: [ccmtools-devel] HelloWorld falls silent

[Egon T. <ego...@ut...>]

Hi Darrell!

> Thanks for the help Egon! OK, I've built java-environment (easy) and
> most of cpp-environment (painful). I see a note in the INSTALL file for
> CCM_Python:
>
> 	-------------------------------------------------------------------- o)
> Install the python component's environment:
> 	   $ confix.py --packageroot=CCM_Python --bootstrap --configure --make
> --targets="all install" But, it does not work because CCM_Python is
> the package root directory of the Python generator environment!!
> 	--------------------------------------------------------------------

This part of cpp-environment is currently not used by the ccmtools.
Actually, Leif is working on a local C++/Python component generator that
creates C++ component logic and delegates to Python business logic (in a
separate CVS branch). Thus, a client handles C++ components while the
Python business logic can be   changed without recompiling.

> I'm trying to build this for packaging with RPM (so I can get others to
> try ccmtools, if it looks promising). Currently I have to sed most of
> the Makefiles to patch the repo location not to install into /usr (BTW,
> what is the repo for?), see below. Is there an easier way to build
> cpp-environment in an intermediate location for later
> installation via RPM?

Hmm, we always use ccmtools together with confix. Thus I did not try to
change the build process in that way.
Maybe Jörg (the confix guru) can answer this question...

> What I'd like to use ccmtools for is creating components which can
> either be used directly from Python or remotely via a C++ CORBA
> server. Do you think this is a reasonable application of ccmtools?
> Also, from the tutorial diagram, it looks like the "local Python
> Component Generator" and the "remote C++ Component Generator" are works
> in progress (perhaps why I cannot compile CCM_Python?). Is
> this right? Any idea if these represents significant work?

Currently, the ccmtools project is focused on a local C++ implementation
of CCM components that can be extended to remote (CORBA) components
transparently.
There is no generator that creates a Python wrapper for a local C++
component - but it would be possible because of the existence of local C++
components...
The remote C++ generator is in progress but can be used (=experimental ;-)

> Thanks for your help and sorry for all of the questions!

You're welcome!

:-) Egon