This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Linking gnu-win32 (X11R6.3) libraries in MS-Developer (*.a -?-> *.lib)
- To: Sergey Okhapkin <sos at prospect dot com dot ru>
- Subject: Re: Linking gnu-win32 (X11R6.3) libraries in MS-Developer (*.a -?-> *.lib)
- From: "Tor M. Aamodt" <aamodt at accessv dot com>
- Date: Mon, 29 Sep 1997 12:50:22 -0400
- CC: "'Arlindo da Silva'" <dasilva at woodmore dot gsfc dot nasa dot gov>, "gnu-win32 at cygnus dot com" <gnu-win32 at cygnus dot com>
- Organization: University of Toronto
- References: <01BCCCB5.4F2EDF30@gater.krystalbank.msk.ru>
I'm a bit confused by your responses ( Arlindo and Sergey ) to my question.
I am trying to debug with the MS Developer Studio (under NT 4.0), and you both
mention using ld, which is part of gnu-win32. How will a new ld fix things if
MSDEV doesn't use the old one (it used a program called link.exe)? Is it not
possible to link to the *.dll's made with gnu-win32 using anything but ld?
Perhaps I am misunderstanding you. Do you mean that remaking the libraries
with a new ld would fix the problem? If so, how does one get the source code
/ new ld?
Some else (peeter_joot@vnet.ibm.com) offered me the reasonable advice that the
Developer Studio probably misinterpretes *.a files and so I (after having
learned how to do this from him) converted libX11.a to .lib format to no avail
(exact same errors). If the code makes and works correctly with g++ under NT,
is it still really likely to be an error in the library, or more likely a
compatibility issue with link.exe?
Thanks,
Tor
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".