Re: Pro*C - Borland C++ problem

From: Allen Hadden <ahadden_at_taratec.com>
Date: 1997/02/27
Message-ID: <3315C28F.6FB5_at_taratec.com>#1/1


hl_at_fiol.brock.dk wrote:
>
> We've recently installed the oracle Pro*C precompiler on our Windows 3.1 based PC's.
>
> The programs developed in Pro*C ( version 2.0.4.2.0 ) are to be used together with
> Borland C++ version 4.52.
>
> After a precompile of the .pc we compile the .cpp under Borland. The compile works well
> but under the link phase, well receive an error with the userexit library sqx16win.lib
> (placed under orawin\pro20\c\lib )
>
> When I try to "look" at the library using Borlands Tlib it states:
>
> Error: Bad Header in input LIB
>
> The same goes for the library SQX17WIN.LIB in the pro21 catalogue, and for the
> SQX16WIN.LIB placed under both FORMS45/USEREXIT and REPORT25/USEREXIT
>
> any clue to what's the problem. I've heard some roumours from different people, saying
> that there has been some problems in the compability of Oracle/Borland library
>

LIB files from different compilers usually have different formats. You are going
to need special LIB files for Borland. If these are just import libraries (for
DLLs), then you should be able to run implib on the DLL to get a LIB file. If
they are static libraries, then you may be in trouble (I think they are).

I think the rumors that you are referring to in the compatability of Oracle and
Borland are related to OCI, not Pro*C. Not sure Pro*C and Borland are supposed
to be compatible.

-Allen

-- 
Allen Hadden
Systems Engineer/Laboratory Application Specialist
Taratec Development Corporation
ahadden_at_taratec.com
Received on Thu Feb 27 1997 - 00:00:00 CET

Original text of this message