Hi all -
I've just created a new CVS module containing the C++ environment for
our generated components. I tried to whip together a build system and
some scanty docs (see INSTALL and README), but I haven't tried building
and installing the module yet.
To check out this module, do the following at a prompt :
$ cvs -d :ext:use...@cv...:/cvsroot/ccmtools co cpp-environment
If I estimate correctly, we'll need to do a few things in the next few
days to make sure this is a smooth transition :
- make sure the environment builds and installs properly. This
shouldn't be too much hassle, but we'll need to mess around
with the Makefile in CCM_Remote/RemoteComponents/. Currently,
it makes a call to ccmtools-idl, which is in the ccmtools
package. We can't have this circular dependency, so we might
need to mess around with how we build the skeletons/stubs
within the cpp-environment module. I think this will end up
being some sort of Confix build solution.
- add some checks to the ccmtools/configure.ac script that see
whether the environment is installed, and enable/disable some
of the generators appropriately. I'll work on this tonight or
tomorrow.
- modify the ccmtools/test/Cpp*Generator/ scripts so that the
environment will be loaded properly during testing. As long
as we can convince Confix to use multiple repositories, this
is no problem.
That's it. Sorry for the breakage in advance, but yet again this is
making the tools a more solid package (I think :). Cheers !
leif
--
Leif Morgan Johnson : http://ambient.2y.net/leif/
|
