Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <31A90D7E3560D511AC7400A0C96B2730012BF2BC@fmsmsx59.fm.intel.com>
From: "Asbenson, Lyndell L" <lyndell DOT l DOT asbenson AT intel DOT com>
To: "'Charles Wilson'" <cwilson AT ece DOT gatech DOT edu>,
   "Asbenson, Lyndell L" <lyndell DOT l DOT asbenson AT intel DOT com>
Cc: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: DLL Win 2000
Date: Tue, 2 Oct 2001 14:39:16 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"


Chuck,
We are just about there, one more question. I have
a gpib-32.dll which now works properly I also have 
a Microsoft C++ gpib_lang_ms.obj file which is a language
interface file. In using the -mno-cygwin I don't get any
errors but when I compile the program and run the .exe
it runs into memory violations. Is there another way of 
using or compiling in language.obj object files?
Thanks,
Lyndell Lee Asbenson


-----Original Message-----
From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu]
Sent: Saturday, September 29, 2001 2:52 PM
To: Asbenson, Lyndell L
Cc: 'cygwin AT cygwin DOT com'
Subject: Re: DLL Win 2000




Asbenson, Lyndell L wrote:

> I have national instruments drivers for a GPIB device and all that they
> offer
> is DLLs and Language interfaces for Borland C++ or Microsoft C++. I have
> also
> look at your DLL conversion process 5 steeps. Is there any tool that will
> convert a DLL 32 bit to a static library where I could use this in the
> Cygwin
> environment?


Sort of.  You can create an gcc-style import library for the DLL (search 
for help/docu on 'dlltool' for more information).  This import lib will 
work with both cygwin's gcc and with mingw's gcc.

However, the odds are that any code you write must be compiled with the 
'gcc -mno-cygwin' option of cygwin's compiler, or you should just use 
the mingw compiler.  The reason for this is that the NI DLL *probably* 
was built to depend on msvcrt.dll, not cygwin1.dll.  Since both of these 
provide runtime services - and you can only have one runtime lib for a 
given app - your app will also have to be linked against msvcrt.dll (not 
cygwin1.dll)  Ergo, -mno-cygwin (or just use mingw comiler, not cygwin 
compiler).  You can check the dependencies of your NI DLL thus:
  cygcheck my_ni_dll.dll

--Chuck

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