From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4a25fdb0a2168f07 X-Google-Attributes: gid103376,public X-Google-Thread: 114f47,4a25fdb0a2168f07 X-Google-Attributes: gid114f47,public From: Marco Gibellini - GBL Subject: Re: Continuus/CM and Alsys Ada(83) Date: 1996/10/03 Message-ID: <3253AAF0.72CB@eurocontrol.fr>#1/1 X-Deja-AN: 186921186 references: <3250E31E.5CE4@eurocontrol.fr> <52rq16$f4@linus.mitre.org> to: Michael F Brenner content-type: text/plain; charset=us-ascii organization: Eurocontrol mime-version: 1.0 newsgroups: comp.software.config-mgmt,comp.lang.ada x-mailer: Mozilla 3.0 (X11; I; HP-UX A.09.05 9000/755) Date: 1996-10-03T00:00:00+00:00 List-Id: Michael F Brenner wrote: > 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 structure. 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 code. 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-69.88.75.68 | B.P. 15 Fax: +33.1-69.88.72.27 | F-91222 Bretigny sur Orge CDX mailto:marco.gibellini@eurocontrol.fr | France