Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: function exported from DLL compiled under Cygwin
Date:	Mon, 17 May 2004 17:55:58 +0100
MIME-Version:	1.0
In-Reply-To:	<457C6AE5782017419D5A7CD0E122EC131DCB4D@ca1xpr08.kla-tencor.com>
Message-ID:	<NUTMEGutSgcOrBLSAQV00000132@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	17 May 2004 16:55:58.0178 (UTC) FILETIME=[D3718C20:01C43C2F]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Yu, Ted
> Sent: 17 May 2004 17:47

> I exported the following function from DLL produced by Cygwin:
> extern "C" int ted( float *data, int rows, int cols )
> {
> 	return cols;
> }
> When I called this function from MSVC, I got exception.

  Isn't this most likely to be caused by msvc and gcc having a different
idea about whether the function is stdcall or cdecl, rather than any kind of
runtime initialisation?  Such a simple function ought to work without any
problem.  (This does assume that you were indeed getting the exception at
the point you call the function, rather than at the point you LoadLibrary
the dll; that would indicate a different problem).


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -