From: Paul G. <pgarceau@at...> - 2002-04-22 21:29:33
Don't know if I have much more to add to this...but think I will attempt to anyway:
On 22 Apr 2002 at 7:36, Earnie Boyd wrote:
> Not unless the Borland object is a MSVC look alike. I was answering
> the question directly without any further insight. As far as
> ignorance, I can't claim any knowledge from experience on the subject
> either. From what I recall Borland's .lib files weren't compatible
> with MSVC or MinGW.
I think that Borlands' .lib files are compatible with msvc (past experience porting between Borland and msvc
is all that I can go on, and that is likely outdated at this point), but are clearly incompatible with Mingw without some
sort of modifications to the file formatting process. (Assumption: you are using latest free Borland/Inprise compiler).
FWIW, when it comes to converting from .lib to .a, it typically seems much easier to simply generate new .a
libraries directly using Mingw tools then it is to generate them indirectly, ie. convert from .lib to .a files.
Borland OBJ format _is_ different from MSVC. Borland uses the old OMF format
as in the DOS time, while Microsoft switched to COFF when targeting Win32. A
LIB for BCC is incompatible with MSVC!
In my test, it seems that MinGW GCC will accept MSVC-style OBJ and LIB files
on the command line directly. Yes, "gcc test.c test1.obj" or "gcc test.c
test1.lib" works and produces correct executables. Borland files won't work.
C++ won't work, either, of course.