From: karl@grebyn.COM (Karl Nyberg)
Subject: Grady Booch's Components Library Compilation Problems
Date: 14 Sep 88 00:02:02 GMT [thread overview]
Message-ID: <8809140002.AA11081@grebyn.com> (raw)
In-Reply-To: 8809132132.AA12787@minotaur.uucp
Date: Tue, 13 Sep 88 14:32:45 -0700
From: Scott Simpson <haven!oberon.USC.EDU!minotaur!simpson%trwarcadia.UUCP>
... Unfortunately, compiling
all the routines requires knowing the dependencies between modules.
Does anybody have a list of the modules in a dependency order? What I
need are a list of the files in dependency order ...
(We are using Verdix Ada as though it matters.)
Yes, it does matter (perhaps). With VADS on UNIX you could try using
a.make -f *.a
That would automatically determine the correct dependency order and compile
things appropriately, assuming that the total number of files doesn't
generate an argument list that's too long for your shell, or otherwise cause
a.make to go catatonic. If you give it the -V (VERIFY) flag in addition, it
will generate the list of compilation commands without executing them, so
you could redirect stdout to a file and edit appropriately to make a shell
script. (That's the long answer - the short one is RTFM!)
There's also a compilation order tool available from the SIMTEL repository,
although I haven't personally used it, and couldn't vouch for it, since I
use a.make instead. I'm not even sure if it has dependencies that might
prevent you from using it in your environment.
-- Karl --
p.s. I still own stock in Verdix.
Karl A. Nyberg karl@grebyn.com, nyberg@ajpo.sei.cmu.edu
Grebyn Corporation karl%grebyn.com@haven.umd.edu
P. O. Box 1144 {decuac,haven}!grebyn!karl
Vienna, VA 22180-1144 703-281-2194
next prev parent reply other threads:[~1988-09-14 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1988-09-13 21:32 Grady Booch's Components Library Compilation Problems Scott Simpson
1988-09-14 0:02 ` Karl Nyberg [this message]
1988-09-19 15:36 ` gbooch
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox