Re: [ccmtools-devel] Directory structure

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

Hi Egon -

> My question to you is, how extensive these changes will be in the
> CppLocalGenerator (two more <<<<<SPLIT>>>>> sections in the MHomeDef
> and MComponentDef Templates and changes in the writeOutput() method)?
> Thus, what I need are the empty *_share.h and *EntryPoint.h files, I
> can fill the templates from the example by myself.

This change was easy to make ... much easier than the Python wrapper
generator is turning out to be. :-/ See the attached patch for the
changes ; I'm going to go ahead and check it in now so you can fill in
the MHomeDef and MComponentDef templates at your leisure.

Also, I named the entry point file %(Identifier)s_entry.h just to keep
with the name_purpose.{cc|h} convention.

> As you know, the ccmtools-c++-configure and ccmtools-c++-make scripts
> copy the *_app.* files into the generated package. This causes some
> problems:
> *) It's not possible to configure and make the component with a single
>    confix call.
> *) If we use more than the generated *_app.* files, we have to copy
>    these files manually into the package directory.

Can we remove the file copying stuff from the ccmtools-c++-* scripts ?
How will this change the test/CppGenerator/test-loader.sh script, and
the tests in that directory ?

leif

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