Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Link failure - against cygwin
Date: Mon, 8 Aug 2005 11:52:06 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <BAY106-F2401756A700DE4555F4F94FBB90@phx.gbl>
Message-ID: <SERRANO2E1ohOiMPAwx000000fc@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Eitan Eliahu
>Sent: 07 August 2005 15:55

> Hi folks, I've added and API function to cygwin and call it from a Linux
> app.
> The new function is included in the new cygwin.dll (dumpbin /EXPORTS
> cyhwin.dll).
> However, I don't know which is the new import library that application
> need to link with.

  When you did 'make install', you should have got a new libcygwin.a
installed into /lib at the same time as you got a new cygwin1.dll installed
into /bin.  If you manually copied the dll into your .bin dir, of course,
this will not have happened.  You should be able to use nm or objdump to
verify that the new function is listed in the import library as well as
having an export from the .dll itself, then everything should work.

  NB:  Save your old cygwin1.dll *and* your old libcygwin.a in case you need
to go back....


    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/