|
From: Teiniker E. <ego...@tu...> - 2003-10-12 19:11:42
|
Hey Leif!
Quoting Leif Johnson <le...@am...>:
> > 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.
Wow, that was really fast!
> Also, I named the entry point file %(Identifier)s_entry.h just to keep
> with the name_purpose.{cc|h} convention.
Yes, that's a good idea.
> > 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 ?
Well, with the new directory structure, we only need the ccmtools-c++-generate
script and some confix calls (for configure, make, install).
> How will this change the test/CppGenerator/test-loader.sh script, and
> the tests in that directory ?
Uff, you are right!
The test-loader.sh must also be changed to handle this new component structure.
The test code in the ccmtools/test/CppGenerator/* directories could be stored in
the same src and CCM_Test sub-directories. To run the test, these
sub-directories are copied to the sandbox directory. After that, the component
can be build and checked in a single confix call - that's the vision ;-)
What do you think about this changes?
:-) Egon
|