Re: [ccmtools-devel] Re: [ccmtools-cvs] ccmtools/CppGenerator CppRemoteGeneratorImpl.java,1.35,1.36

[Teiniker E. <ego...@tu...>]

Hey Leif!

Quoting Leif Johnson <le...@am...>:

> Sorry I keep bothering you about this, but we really need to have
> Makefile.am files in the environment files directories. These
> Makefile.am files are purely ccmtools autotools files ; they have no
> relationship with the Makefile.am files that Confix creates. The
> ccmtools autotools files are responsible only for installing and
> uninstalling the environment source trees. We have to install the source
> trees so that binary-only distributions of the CCM Tools will be able to
> include the source files for creating component environment libraries.
>
> I assume you've been having problems with these files because of an
> unfortunate coincidence : Confix happens to create Makefile.am files
> when you build the component environment libraries locally, inside the
> ccmtools source tree. Since there's not really any way around this, you
> *cannot* build the environments directly in the CCM Tools source tree !
>
> Instead, component developers must use either (a) the *installed*
> environment files source trees, or (b) a copy of the environment source
> trees. Actually, the test/CppGenerator/test-loader.sh script fakes an
> installation of the environment files :
>
>   data_dir=${sandbox_dir}/share/${PACKAGE}
>   :
>   :
>   for f in ${abssrcdir}/*Generator/*Environment ; do
>   ln -s $f ${data_dir} ; done
>
> And then the ccmtools-c++-environment script copies the files to
> /tmp/ccmtools-cpp-environment directory, and calls confix to make and
> install them.
>
> I won't add back the Makefile.am files until you give the ok. But we
> must have these files in there before we do another release, because
> binary distributions will not be able to include the environment source
> trees otherwise.

Yes you are right in every point!
So, please add the Makefile.am files (again) - sorry for these troubles...

:-) Egon