[ccmtools-devel] Re: [ccmtools-cvs] ccmtools/CppGenerator Makefile.am,1.9,1.10

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

Hi hi -

I hope these changes I checked in weren't too drastic. You probably
noticed ; I separated the environment/{local|remote} directories into
CppGenerator/Cpp{Local|Remote}Environment, it seemed to make more sense
with the existing directory structure.

On Tue, 2003-12-16 at 04:52, tei...@us... wrote:

> - The environment files should not be built at ccmtools compile-time.
>   Thus I removed these lines from Makefile.py The environment files
>   will be compiled by the component developer using Confix calls.

Right, but the recent Makefile additions don't actually build the
environment files ; they just install the *.cc, *.h, and Makefile.py
files into $prefix/ccmtools/share/Cpp{Local|Remote}Environment/blah as
data ... no compiling involved, just copying. Just like the templates.

The reason for this is that when we distribute binary versions of the
CCM Tools (i.e. .deb or .rpm files) then we'll have to provide these
environment files in some sort of installed location. Normally I'd put
the header files in
$prefix/include/ccmtools/Cpp{Local|Remote}Environment/blah, but with
*.cc files, we can't do that, and Confix is happier with the *.cc and
*.h and Makefile.py files all together. Hence they get installed in
$prefix/ccmtools/share/ for the moment.

I'm going to revert this checkin unless you object ... we have to
install these files as data somewhere, just like the templates. The only
debatable thing is where we install them.

> + To make the ccmtools compile, I added these empty templates to the
>   CppPythonTemplates directory.

Sorry about that ; I have some templates for these on my machine but
haven't checked them in yet. I'll try to do that today. I'll also work
on removing the environment stuff from the generators today ; should
clean up a lot of the code. Yay !

leif

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