From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jim.Totten@barco.com
To: cygwin@sourceware.cygnus.com
Subject: RE: import libraries for 3rd-party DLLs
Date: Wed, 10 Mar 1999 09:39:00 -0000
Message-id: <1DB6D0B30846D111B4860000F8D02CB517C78A@tucmex01.barco.com>
X-SW-Source: 1999-03/msg00328.html

I am trying to use a third party msvc++ .lib file as well.  I was able
to create export and import files using the method mentioned often on
this list and in the users manual (nm followed by a dlltool) and my gcc
program seems to *link* without an errors - however when I execute the
program a window appears with the following message:

"The application or DLL is not a valid Windows NT image."

I saw in the archives someone else who got this same error message, but
there were no follow-ups to the post.  Anybody got some ideas about what
I could be doing wrong?

Thanks,

jt

	-----Original Message-----
	From:	Richard Hellicar (EML)
[SMTP:Rick.Hellicar@eml.ericsson.se]
	Sent:	Wednesday, March 10, 1999 10:39 AM
	To:	'cygwin@sourceware.cygnus.com'
	Subject:	import libraries for 3rd-party DLLs

	Hello,
	                                     
	                                                              
	I'm trying to create an "import library" to allow me to use gcc
with a
	third-party DLL.
	I tried the .lib files supplied with the DLL, but neither worked
(one was
	for MS, which
	did compile, but complained about entry points when executed,
the other for
	Borland).
	                                                              
	The Cygwin User's Guide (Delorie, Humblet, Noer) suggests a
method in
	Chapter 4
	("Linking against DLLs").  However, if I run nm on *any* dll,
not just the
	one I'm trying
	to use, it tells me "No symbols in xyz.dll"

	In February, Gary Vaughan posted another method of producing
import
	libraries;
	you *can* produce a library in this way, but the linker chokes
on undefined
	references when you use it.

	Can of the cygwin gods tell me:
	1. Should I expect either the MS or Borland .lib files to be
compatible ?
	2. Is there a way of converting incompatible lib files ?
	3. Why doesn't nm find symbols in *any* DLL (try: for i in
	/winnt/system32/*.DLL; do nm $i; done)
	4. exactly what *is* supposed to be in a .def file; should the
@4,@8  stuff
	be in
	  there or not ?  Semi-colons ?

	I'm running cygwin B20.1 and  gcc version egcs-2.91.57 19980901

	Thanks in advance to you all


	Rick Hellicar
	-- 






	--
	Want to unsubscribe from this list?
	Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jim.Totten@barco.com
To: cygwin@sourceware.cygnus.com
Subject: RE: import libraries for 3rd-party DLLs
Date: Wed, 31 Mar 1999 19:45:00 -0000
Message-ID: <1DB6D0B30846D111B4860000F8D02CB517C78A@tucmex01.barco.com>
X-SW-Source: 1999-03n/msg00328.html
Message-ID: <19990331194500.LyLocn5_prDgCY7mnJ2nGuPa1NIuyGBHKLAXW71JPMs@z>

I am trying to use a third party msvc++ .lib file as well.  I was able
to create export and import files using the method mentioned often on
this list and in the users manual (nm followed by a dlltool) and my gcc
program seems to *link* without an errors - however when I execute the
program a window appears with the following message:

"The application or DLL is not a valid Windows NT image."

I saw in the archives someone else who got this same error message, but
there were no follow-ups to the post.  Anybody got some ideas about what
I could be doing wrong?

Thanks,

jt

	-----Original Message-----
	From:	Richard Hellicar (EML)
[SMTP:Rick.Hellicar@eml.ericsson.se]
	Sent:	Wednesday, March 10, 1999 10:39 AM
	To:	'cygwin@sourceware.cygnus.com'
	Subject:	import libraries for 3rd-party DLLs

	Hello,
	                                     
	                                                              
	I'm trying to create an "import library" to allow me to use gcc
with a
	third-party DLL.
	I tried the .lib files supplied with the DLL, but neither worked
(one was
	for MS, which
	did compile, but complained about entry points when executed,
the other for
	Borland).
	                                                              
	The Cygwin User's Guide (Delorie, Humblet, Noer) suggests a
method in
	Chapter 4
	("Linking against DLLs").  However, if I run nm on *any* dll,
not just the
	one I'm trying
	to use, it tells me "No symbols in xyz.dll"

	In February, Gary Vaughan posted another method of producing
import
	libraries;
	you *can* produce a library in this way, but the linker chokes
on undefined
	references when you use it.

	Can of the cygwin gods tell me:
	1. Should I expect either the MS or Borland .lib files to be
compatible ?
	2. Is there a way of converting incompatible lib files ?
	3. Why doesn't nm find symbols in *any* DLL (try: for i in
	/winnt/system32/*.DLL; do nm $i; done)
	4. exactly what *is* supposed to be in a .def file; should the
@4,@8  stuff
	be in
	  there or not ?  Semi-colons ?

	I'm running cygwin B20.1 and  gcc version egcs-2.91.57 19980901

	Thanks in advance to you all


	Rick Hellicar
	-- 






	--
	Want to unsubscribe from this list?
	Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com