Re: PRO*C config problems in general
Date: Fri, 15 Dec 2000 15:49:44 GMT
Message-ID: <91deil$1mn$1_at_nnrp1.deja.com>
[Quoted] If you are familiar with C/C++ and your compiler, then the specifics of [Quoted] [Quoted] getting the precompiler going aren't that tough. The Windows version of the precompiler comes with a getting Started manual (if you can't find [Quoted] [Quoted] it, the got read it online under the documentation link at OTN -- technet.oracle.com) that explains a lot of the compiler specifics in step-by-step form.
Here are the general steps to getting a precompiler program precompiled
and working.
1) Run the precompiler against the embedded SQL Source. You can use the
command line compiler or configure a tool from the menu or even
configure a custom build step for the *.PC source file in your project.
2) Assuming the first step is complete, you now have a *.C or *.CPP
file that needs to be included into your project.
3) Include the platform specific (and compiler specific on Windows)
SQLLIB into the project list of files (or as a linker include
directive).
4) Build the project.
[Quoted] Read the getting started manual for your version. Oracle's support for the Borland compilers has been on and off over the various versions and [Quoted] you may have a version of the precompiler that either doesn't come with [Quoted] Borland libraries, or comes with a version of the libraries that will [Quoted] not work with your version of the Borland compiler.
--
-cheers
DW
[Quoted] "It is a kind of good deed to say well; and yet words are not deeds. -William Shakespeare"
Sent via Deja.com
http://www.deja.com/
Received on Fri Dec 15 2000 - 16:49:44 CET