[ccmtools-devel] Re: CCM Tools questions

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

I'm cc'ing this to the ccmtools-devel list ... seems to be of general
interest for the (potential) other folks out there. :)

On Mon, 07 Apr 2003, Egon Teiniker wrote:

>Hey Leif!
>
>I have some questions about ccm tools:
>
>*) typedef
>Can we support the typedef construct (maybe in the next release)?
>e.g.
>typedef string myString;
>
>interface Console {
>  long println(in string s2);
>};
>
>component Hello
>{
>  attribute MyString prompt;
>  provides Console console;
>};
>
>home HelloHome manages Hello
>{
>};

I thought the tools already handled this fine. I'm going to try this out
and see what goes wrong, because we definitely need to do typedef properly.
As soon as it's fixed we can get a quick 0.2.1 release out ! :)

>*) CCM_Local/user_types.h
>will be generated in every ccmtools-c++-generate call, this can be a problem
>when installing different component projects - the last install wins!
>Is there a possibility to name the user_types.h file like the package?

Hmm, i'll look into it. It seems like a solution to this might lie with
Confix, i.e. have Confix install the headers not into a global dir, but
somewhere under ${prefix}/include.

The way I've seen other projects (glib, gtk, gnome, gstreamer) do this is
to install their headers into ${prefix}/include/PACKAGE-VERSION and then
use pkg-config (or, in our case, Confix's module repository) to figure out
which include dir to use when compiling other packages that use the
installed headers. This might require some fiddling with namespaces in our
case though ?

>*) Documentation
>I think we should provide the following docs:
>  - CCM Tools Tutorial
>    Describes the first steps in using the CCM Tools
>  - CCM Tools User's Guide
>    Describes the using of CCM Tools in more details (IDL->C++ Mapping, install
>file structure, ...)
>  - CCM Tools Developer's Guide
>    Describes the structure and the details of the implementation and how to add
>a new generator...
>Do you agree?

Definitely. The "developer's guide" seems to be closest to the doc in
ccmtools/doc/manual, which I estimate is 25 % done. I'll likely spend a lot
of time this week working on that. You've done an excellent job on the
tutorial, which leaves the user's guide ... just an expansion of the stuff
in the tutorial, or a completely different beast ?

leif

--
Leif Morgan Johnson . http://ambient.2y.net/leif/
IAESTE trainee      . http://www.iaeste.org/
Salomon Automation  . http://www.salomon.at/