From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f722a2869f777d70 X-Google-Attributes: gid103376,public From: jerry@jvdsys.stuyts.nl (Jerry van Dijk) Subject: Re: How to Link Borland C++ object files with GNAT Date: 1999/04/08 Message-ID: #1/1 X-Deja-AN: 464205288 References: <370CF3A4.55001E84@harris.com> Organization: * JerryWare *, Leiden, Holland Newsgroups: comp.lang.ada Date: 1999-04-08T00:00:00+00:00 List-Id: Dennis Quinones (dquinone@harris.com) wrote: : I have PCMCIA drivers written in Borland C++ and I am trying to link : them to : my main application written in Ada (GNAT 3.11). Borland C++ generates : *.obj : files which are not compatible to *.o files. : Is there a way to convert the *.obj files to *.o files? : Or any other suggestions would be greatly appreacited. Well, if this is really C++ code (and not C compiled by a also C++ capable compiler), moving from .obj to .o is the least of your worries. BC will use its own unique way of encoding functions, exceptions, namespaces, and such, that GNAT, of course, knows nothing about. That does not mean it cannot be made to work, it does mean it will involve a lot of work. I know of no way to convert from .obj to .o format (although PE includes Coff, so this should be relatively easy to do). This assumes of course, that you will also initialize all runtime libraries and DLL's properly yourself. The easy way out is compile your drivers into a DLL, and then build a GNAT style (.a) import library for it. -- -- Jerry van Dijk | Leiden, Holland -- Team Ada | jdijk@acm.org -- see http://stad.dsl.nl/~jvandyk