Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
X-Authentication-Warning:	modi.xraylith.wisc.edu: khan owned process doing -bs
Date:	Wed, 31 Mar 1999 11:51:02 -0600 (CST)
From:	Mumit Khan <khan AT xraylith DOT wisc DOT edu>
To:	Kehl Hubertus <Hubertus DOT Kehl AT icn DOT siemens DOT de>
cc:	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: Cygwin + Borland Libs ? Cygwin + X2C ?
In-Reply-To:	<197A67E1DB8DD211A4670008C728B7040B64C0@mchh220e.demchh201e.oen.siemens.de>
Message-ID:	<Pine.SUN.3.93.990331114700.26550D-100000@modi.xraylith.wisc.edu>
MIME-Version:	1.0

On Wed, 31 Mar 1999, Kehl Hubertus wrote:

> 1. Is it possible to link Borland C++ (3.1 or 4.5) objects or libraries with
> Cygwin, or
> is there any way to convert them to the cygwin object file format ?

Borland uses OMF and Cygwin uses PE-COFF, so unless you can convert OMF to
COFF, there's not a chance (didn't borland supply a tool for this?). Even
if you could convert the format, the references to runtime within these 
objects will be wrong and it just won't work correctly. However, if the
Borland object files were compiled statically, it may work.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -