Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun-barr!apple!oliveb!amdahl!rtech!squid!edg
From: edg@squid.rtech.com (Ed Goldman)
Newsgroups: comp.databases
Subject: Re: ingres, alt method for building abf applications
Message-ID: <2891@rtech.rtech.com>
Date: 11 May 89 15:31:57 GMT
References: <1506@infinet.UUCP> <511@daitc.daitc.mil>
Sender: news@rtech.rtech.com
Reply-To: edg@squid.UUCP (Ed Goldman)
Organization: Relational Technology, Inc.
Lines: 30

In article <511@daitc.daitc.mil> jkrueger@daitc.daitc.mil (Jonathan Krueger) writes:
>In article <1506@infinet.UUCP>, sena@infinet (Fred Sena) writes:
>>Unix utilities tend to be set up such that they can run in a "non-interactive"
>>mode.  That means that you can run a command on a bunch of files, go out to
>>lunch, come back, and check to see which files had errors and what they were.
>>In abf, however, the "Image" command forces you to sit there and press the
>><return> key several times for each module which has an error.
>
> [other discussions about abf deleted...]

Some hints:

the file ~ingres/files/utcom.def is used by abf to compile source depending
upon a file's extension.  Take a look at it.  You should be able to see
where you can put -g flag (or any cc flag for that matter) by directly
editing this file on the "cc" lines.

the file ~ingres/files/utexe.def has templates of the flags used by ingres
executables.  Check out oslosq.  I think you'll be able to figure out how
to compile .osq files by looking here.  I can't recall offhand, but I think
you'll need to give ite it: .osq filename, database name, framename,
outputfile name (.qc file).

setenv II_UTEXE_TRACE /dev/tty will output to screen the ld command line.
(Not in all releases and definately *NOT* supported)

newer ingres releases have an ~ingres/files/utld.def file which abf uses
aS a template to build the ld command line.

-edg-