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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID,
	RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,df13d4f4aa9842dc
X-Google-Attributes: gid103376,public
From: "bob" <bklungle@junque.com>
Subject: Re: Green Hills Ada library question
Date: 1998/09/15
Message-ID: <01bde0c5$2b8d46a0$0e2915c0@w95>#1/1
X-Deja-AN: 391388263
References: <6tjgph$661$1@nnrp1.dejanews.com>
Organization: B & D Associates
X-NETCOM-Date: Tue Sep 15  9:20:52 AM PDT 1998
Newsgroups: comp.lang.ada
Date: 1998-09-15T09:20:52-07:00
List-Id: <comp.lang.ada>

I sympathize with you. We started the same thing about 8 months ago.
The system is now mostly working (with many bugs we worked around because
Green Hills REFUSED to fix them).

The first thing we did was make a directory with symbolic links to the
sources 
(over 1100 Ada packages and C files). This allowed the workers to continue
fixing
their code without moving things around. Then a test generate of some
components
(generate a builder file). Then with vi and emacs, fairly quickly hand
built a complete
filename.bld file, structured as needed. From here on, Multi did its job.
We then 
migrated over time to SCCS control with a build map to a development
directory.

Believe me, most of our users are disgusted with the Green Hills/Multi
system
for Ada (they came from a VERDIX/Rational environment), but there was no
other
available with vxworks targeted to the system we needed. We are seriously
thinking
of contacting ACT and see if there is a better solution there.

If you would like more, no need to air laundry on USER group.

bob
Raytheon Systems
bklungle@ix.netcom.com

dennison@telepath.com wrote in article <6tjgph$661$1@nnrp1.dejanews.com>...
> I'm trying to do an initial build of an Ada system we have here using the
> Green Hills AdaMulti environment on WindowsNT. Our system currently has
371
> source files scattered over 42 different directories.
> 
> Green Hills tech support claims their system has no automatic build
process,
> and I will have to go into their IDE and *manually* add all 371 files to
a
> build file.  That file will also have to be *manually* maintained. (Can
you
> say "error prone"?). They do have an "adareg" command, but no "compile
> obsolete adareg'ed units" command. They have the ability to compile
obsolete
> units that are listed in the build file, but no "put these units in the
build
> file" command.
> 
> I have more than a little trouble believing all this, as it would be the
only
> Ada compiler I have ever worked with (out of 8) that lacks some way to
> automaticaly build and maintain a system. Can someone else who has worked
with
> Green Hills tell me how this is done?
> 
> --
> T.E.D.
> 
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum
>