* Gnatmake query
@ 1996-10-31 0:00 John English
1996-11-02 0:00 ` Robert Dewar
0 siblings, 1 reply; 2+ messages in thread
From: John English @ 1996-10-31 0:00 UTC (permalink / raw)
Can anyone tell me why, when building a program which has already
been built and is fully up-to-date, gnatmake still does gnatbind -x
followed by gnatlink? Is there a way of convincing it otherwise?
---------------------------------------------------------------
John English | mailto:je@brighton.ac.uk
Senior Lecturer | http://www.comp.it.bton.ac.uk/je
Dept. of Computing | fax: (+44) 1273 642405
University of Brighton |
---------------------------------------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Gnatmake query
1996-10-31 0:00 Gnatmake query John English
@ 1996-11-02 0:00 ` Robert Dewar
0 siblings, 0 replies; 2+ messages in thread
From: Robert Dewar @ 1996-11-02 0:00 UTC (permalink / raw)
iJohn English asks
"Can anyone tell me why, when building a program which has already
been built and is fully up-to-date, gnatmake still does gnatbind -x
followed by gnatlink? Is there a way of convincing it otherwise?"
Yes, it is easy to tell you why -- you are not using the latest version
of GNAT, in which this behavior is modified to only bind and link if
necessary. For example, in OS/2:
[OS2-F:\emx\gnu\gcc-2.7\ada]gnatmake a
gcc -c a.adb
gnatbind -x a.ali
gnatlink a.ali
[OS2-F:\emx\gnu\gcc-2.7\ada]gnatmake a
gnatmake: "a.exe" up to date.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1996-11-02 0:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1996-10-31 0:00 Gnatmake query John English
1996-11-02 0:00 ` Robert Dewar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox