> I am very interested in both of these tools, but what do you mean by
> integrating them together? Do you mean using CCM to manage the
> configuration of your source code and documentation, to be
> compiled by Alsys?
Yes. This is exactly what we want, but our setup only allow us to
do this with the help of some (relativly) complex makefiles and
shell scripts rather than using the Continuus/OM tool.
One of the projects we have is relativly large (2000+ compilation
units), so the Ada library is huge and a complete library compilation
(using Alsys AdaMake) takes in the order of 2 hours. There are usually
several versions of each project under concurrent development so to
hold a full Ada compilation libray for each sqa, integration and
working version of the project is unfeasable. Although we are trying to
restructure, we currently have to work with this monolithic project
We do not want to control the Ada libraries as they can be regenerated
from the source, and change freequently as developers modify and test
The question is, how do other users manage the relationship between
each Continuus project version and the Alsys Ada library corresponding
to that version?
Our current strategy is to hold a 'full' library for each complete
sqa and integration library, and use these as 'parent' libraries
(Alsys terminology) for each working project version. Our makefiles
and scripts then try to manage the relationships between the Alsys
Ada libraries and Continuus project versions.
Although this messes up developer's libraries sometimes (e.g. when the
subunits of an Ada package change), it works most of the time. We also
have problems with changing configurations e.g. using an old version of
somthing in a developer's view, which the compiler does not recompile
as it 'sees' a newer version in the integration library.
Does anyone else manage large Ada projects using Continuus, and if so,
how? I get the impression that Continuus is not really targetted to
controlling objects with Ada like dependencies between them.
Continuus/OM does however seem to have specific support for 'C'
source and include files.
Marco Gibellini (SEU) | Eurocontrol Experimental Centre
Phone: +33.1-126.96.36.199 | B.P. 15
Fax: +33.1-188.8.131.52 | F-91222 Bretigny sur Orge CDX