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
To:	cygwin AT cygwin DOT com
Subject:	Building DLLs to be loaded from Visual Basic
From:	Massimiliano Mirra <mmirra AT libero DOT it>
Date:	Mon, 31 Mar 2003 11:43:44 +0200
Message-ID:	<87pto76fcf.fsf@prism.localnet>
User-Agent:	Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2
MIME-Version:	1.0

I have been asked to write some code to be integrated in a legacy
Visual Basic application.  This code should be available as a DLL.

I have built the i686-pc-linux -> i686-pc-cygwin cross compiler and
used it with success to compile a few small executables.  Reading
mailing list archives I found contrasting thoughts as to whether and
how DLLs built with the cygwin toolchain can be loaded from
applications written in other languages.  Messages span over more than
five years, and there are references to ``you must do this for this
cygwin version, but with the next...'' so I'm finding it difficult to
pull together a present picture.

My questions:

- is anybody today successfully building DLLs with cygwin (not
  mingw32) and loading them from Visual Basic (or other languages)?

- is documentation about the process available?


Thanks
Massimiliano

--
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/

- Raw text -