Re: [ccmtools-devel] ccmtools/environment

[Leif J. <le...@am...>]

Hi -

I have to admit I'm a bit lost on this subject.

Here's my understanding. We're trying to provide a way for CCM Tools
users (i.e. component developers) to create the necessary environment
for using any of a number of different CORBA ORBs (Tao, Mico, ORBit,
etc.). We could do this by either providing some sort of complimicated
development script that would generate Confix development files
depending on the name of the ORB the developer wants to link with. Or we
can just provide a directory of the appropriate Confix files, and let
the component developer compile their components with the appropriate
ORB environment files as part of the component source tree. Let me know
if I'm mistaken on this.

On Thu, 04 Dec 2003, Joerg Faschingbauer wrote:

> >>>>> "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>
> 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.

So, if I understand, these new directories are necessary for holding the
Confix Makefiles and other supporting development information to build
CCM Tools components using these different ORBs. Right ? Is the
ccmtools-c++remote-environment script responsible for copying the
appropriate directory to the component source tree ?

> 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?

My only suggestion at this point is a package maintenance one : Because
these environment files are appropriate only for the C++ generator
family, we should move the entire ccmtools/environment/ directory to
ccmtools/CppGenerator/environment/. If you don't have any objections I
can do this tomorrow or the next day.

And are these environment directories to be installed when the CCM Tools
are installed ? Seems like they're analogous to the template
directories, so yes, right ? My suggestion for installation is
$(pkgdatadir)/CppGenerator/environment/.

> 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.

So this is a utils package that's part of Confix, or a Salomon internal
package ? I'm a bit confused. Also, I'd like to clarify the separation
between the WX_Utils package and the CCM_Utils package ... which is
which ?

leif

--
Leif Morgan Johnson : http://ambient.2y.net/leif/