Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: linking cygwin built dll with Borland C++Builder X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Date: Thu, 23 May 2002 20:51:17 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Dennis Jarosch" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4NAqbp23874 > -----Original Message----- > From: Dennis Jarosch [mailto:ya_luva@uni.de] > Sent: Thursday, May 23, 2002 8:46 PM > To: Robert Collins > Cc: cygwin@cygwin.com > Subject: Re: linking cygwin built dll with Borland C++Builder > > > Hi Rob! > > Robert Collins wrote: > > Mixing C++ between compilers generally doesn't work. See > the c++-faq > > lite for more details. > > > > Rob > > Maybe I just misunderstood you, but the lib/dll consists of > pure C-code, > no C++ involved. Of course my Wrapper uses C++ code, but I am not > linking any C++ code from gcc! Oh. Well there are some examples in the archives IIRC. I don't have borland C so I can't test this for comparison. You should get the lib to allocate and free it's own memory though, that should address some of your problems. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/