From: Teiniker E. <ego...@tu...> - 2003-12-04 02:48:14
|
Hi all! There is a new ccmtools/environment directory that contains some C++ and IDL files needed for creating environment libraries for components. environment/ |-- external | `-- mico |-- local `-- remote |-- CCM_Session_Container `-- remoteComponents We need an external/mico package that tells confix where to find the mico libraries and, for remote components, the CCM_Session_Container and the remoteComponents package. Note that (except for external/mico) the environment packages for local and remote components can be installed using the ccmtools-c++-environment and ccmtools-c++remote-environment scripts. In that case, the source files are created from CppGenerator templates. But, there is a serious drawback using these scripts. Some of the environment sourc code (external/mico, etc.) are also part of the WAMAS-X framework that is the main user of the ccmtools. Thus, we need a flexible way to decide which package to install. I think that the ccmtools/environment directory can be a good solution, because it leaves the decision of what packages are needed and what packages are already installed by the component developer. He has to call confix for the needed packages. So, what do you think about this idea? :-) Egon PS: The WX::Utils (a substitution for the old CCM_Utils) could be distributed in ccmtools/environment/local too! |