Re: [ccmtools-devel] ccmtools/environment

[Joerg F. <jf...@sa...>]

>>>>> "Egon" == Teiniker Egon <ego...@tu...> writes:

Egon> Hi all!
Egon> There is a new ccmtools/environment directory that contains some C++ and IDL
Egon> files needed for creating environment libraries for components.

Egon> environment/
Egon> |-- external
Egon> |   `-- mico
Egon> |-- local
Egon> `-- remote
Egon>     |-- CCM_Session_Container
Egon>     `-- remoteComponents

Egon> We need an external/mico package that tells confix where to find the mico
Egon> libraries and, for remote components, the CCM_Session_Container and the
Egon> remoteComponents package.

Egon> Note that (except for external/mico) the environment packages for local and
Egon> remote components can be installed using the ccmtools-c++-environment and
Egon> ccmtools-c++remote-environment scripts. In that case, the source files are
Egon> created from CppGenerator templates.
Egon> But, there is a serious drawback using these scripts. Some of the environment
Egon> sourc code (external/mico, etc.) are also part of the WAMAS-X framework that is
Egon> the main user of the ccmtools. Thus, we need a flexible way to decide which
Egon> package to install.
Egon> I think that the ccmtools/environment directory can be a good solution, because
Egon> it leaves the decision of what packages are needed and what packages are
Egon> already installed by the component developer. He has to call confix for the
Egon> needed packages.

Egon> So, what do you think about this idea?

The external/mico thing is a major pain in the ass. Google just told
me that there is a more sophisticated autoconf piece in the autoconf
macro archive
(http://www.gnu.org/software/ac-archive/htmldoc/ac_pkg_mico.html). As
Confix comes with that archive, it would be fairly easy to integrate
it. I'd give it a try over the weekend, if you want. AC_PKG_MICO
doesn't know of CCM however, but we're not using that anyway.

Having a confix module for mico would be a good example for how
external packages are glued into confix, so it's not a bad idea to put
it in the utils package.

Joerg