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,FROM_ADDR_WS,
	INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,71d0395339b53c4d,start
X-Google-Attributes: gid103376,public
From: "W. Wesley Groleau (Wes)"
Subject: Answer to recent alsys plea...
Date: 1996/03/27
Message-ID: <9603271933.AA08706@most>#1/1
X-Deja-AN: 144499504
sender: Ada programming language <INFO-ADA@VM1.NoDak.EDU>
comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
mailer: Elm [revision: 70.85]
newsgroups: comp.lang.ada
Date: 1996-03-27T00:00:00+00:00
List-Id: <comp.lang.ada>

Well, stubbornness paid off.  In case anyone else is
up a creek without a manual, here is the trick
(skipping all the things that DIDN'T work):

DISCLAIMER: It worked on an HP RISC box with Alsys 5.5.2A
and ADAWORLD. I know nothing about other Alsys platforms.
(Don't know much about this one either)

When you want to link (bind) an executable with some
source files YOU have changed without touching the
"main" library and without manually copying and compiling
all the files that depecnd on the units you are changing:

1. your library directory must be a child library of
   the library for what you are modifying.

2. Do the following command sequence.  (Not verbatim; pay
   attention and think!)

PROMPT> adacli
Alsys Ada V5.5.2A
Copyright (C) Alsys, 1985, 1991. All rights reserved.
Ada.w
Workbench.make
    (lib    => <path_to_your_ada_library>,
...  select => (root      => <ada_name_of_the_main_program>,
...             sources   =>
 <shell_pattern_matching_the_files_you_have_changed>,
...             units     => obscelescent),
...  display=> (warnings  => yes),
...  prepare=> (recompile => locally,
...             bind      => yes),
...  invoke => (file      => <file_to_put_commmands_in>,
...             executed  => no)         );
Workbench.quit
Ada.Quit

3. Edit the above file.  If there are any EXTREMEMLY long lines,
   they may have been split.  You must rejoin them so that the next
   step will not choke on the file.  (Hint: If they are in Ada syntax,
   they should be accepted.  Environment variables may be used within
   strings to shorten things.)

4. More ADAWORLD stuff:

PROMPT> adacli
Ada.Invoke ( File => <file_you_put_commmands_in> );
--
---------------------------------------------------------------------------
W. Wesley Groleau (Wes)                                Office: 219-429-4923
Senior Trial & Error Grunt                                FAX: 219-429-5194
Magnavox - Mail Stop 10-40                               Home: 219-471-7206
Fort Wayne,  IN   46808              elm (Unix): wwgrol@pseserv3.fw.hac.com
---------------------------------------------------------------------------