Re: PRO*C config problems in general

In article <91dhoq$4l4$1_at_nnrp1.deja.com>,   chiappa_at_my-deja.com wrote:
> Thanks for your answer; I will post some coments after your lines :
>
> In article <91deil$1mn$1_at_nnrp1.deja.com>,
> DriftWood <drift_wood_at_my-deja.com> wrote:
> > If you are familiar with C/C++ and your compiler, then the specifics
 of
> > getting the precompiler going aren't that tough.
>
> basically this is the problem : I was familiar only with older
 ambients
> (like Turbo C) - no projects, no need to config the libs - only put
> them on the directory, and so on.
>
> >The Windows version of the precompiler comes with a getting Started
 manual (if you can't find
> > 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.
> >
>
> AFAIK, it explains only until the step of putting the PRO*C in the
> Tools menu - from here, it go to programming examples, no hints about
> makefiles, projects, libraries specifications, etc. But I will give it
> one more try, and I will try to use your general tips.
> In time : you know any other source of information to do it ?
>
> > Oracle's support for
> > the Borland compilers has been on and off over the various versions
 and
> > you may have a version of the precompiler that either doesn't come
 with
> > Borland libraries, or comes with a version of the libraries that
 will
> > not work with your version of the Borland compiler.
> >
>
> Well, I mentioned Borland C only because I have this thing - if
 needed,
> I can get out the MS C. The main objective here is to build some small
> progs acessing Oracle, so basically I can use anything I want, in any
> version, in AIX or Windows NT (the main OSs here).
>
> Thank you again,
>
> J. Laurindo Chiappa
>
> Sent via Deja.com
> http://www.deja.com/
>

You are correct in the assertion that Oracle does not clearly define what to do and when.

Your first task is to get used to the development environment you wish to work in. Personally, the pc-based IDE environment is less work. Their projects ie makefiles are reasonably automatic. Within the pc area, MS Visual C++ is the best supported by Oracle.

The Unix side is a little less obvious. You need to create makefiles as the number of libraries (at least for Solaris) is quite large and somewhat convoluted. Major additions are the .pc.cpp command which is detailed in several places. The rest is straight forward. The last install that I worked with had only one makefile with the appropriate libaries and code defined. But then again, one is enough.

Personally, I prefer to use proC. It is more obvious what you are doing and I am reasonably sure anything that can be done in OCI can be done in proC. OCI has too many parameters in each function. The only thing that I ever liked in OCI was a set of wrapper functions that I got called OTL (
http://www.geocities.com/skuchin/otl/home.htm ), that added some features not avialable directly in proC.

Again, the proC is generally more obvious to read, and if you are religious on building your code, you can get some good code.

--
Michael Krolewski
Rosetta Inpharmatics
mkrolewski_at_rii.com
              Usual disclaimers

--
Michael Krolewski
Rosetta Inpharmatics
mkrolewski_at_rii.com
              Usual disclaimers


Sent via Deja.com
http://www.deja.com/