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
Date: Wed, 19 Mar 2003 13:38:45 -0500
From: Jason Tishler <jason AT tishler DOT net>
Subject: Re: Building a win32 python extension from cygwin?
In-reply-to: <20030319174316.RBXK25382.imf58bis.bellsouth.net@tiger2>
To: cygwin AT cygwin DOT com
Mail-followup-to: cygwin AT cygwin DOT com
Message-id: <20030319183845.GE2536@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <20030319174316 DOT RBXK25382 DOT imf58bis DOT bellsouth DOT net AT tiger2>

Greg,

On Wed, Mar 19, 2003 at 12:53:49PM -0500, Greg Freemyer wrote:
>  >>  > My problem was that libpython2.2.dll could not be found in the
>  >>  > specified path.
> 
>  >>  Please run cygcheck on your .exe (installation package) and post
>  >>  the output.  For example:
> 
>  >>  $ cygcheck foo.exe
> 
> ===
> $ cygcheck rdiff-backup.exe
> Found: .\rdiff-backup.exe
> .\rdiff-backup.exe
>   C:\cygwin\bin\libpython2.2.dll
>     C:\cygwin\bin\cygwin1.dll
>       C:\WINNT\System32\KERNEL32.dll
>         C:\WINNT\System32\ntdll.dll
>   C:\cygwin\bin\cygz.dll
> ===

The output from cygcheck explains your "libpython2.2.dll could not be
found" problem.

> If those are the only dependencies, maybe it would not be too bad to
> just build up a deployment CD with the above on it.

Actually, you could get rid of the cygz.dll dependency by linking with
zlib statically.  Ditto for libpython2.2.dll once I support Cygwin
Python with a static core (which is dependent on Cygwin ld supporting
exports from a .exe).  However, the cygwin1.dll dependency cannot be
eliminated unless you use Mingw.

>  >>  If _librsync is dependent on libpython2.2.dll, then the above
>  >>  error make sense.
> 
> Please, don't worry about this.

OK.  I was just trying to understand the issues involved.

> By following the recipe you pointed at, I think I can eliminate this
> issue.

Good.

> But it looks like it is.  (Especially not good since I am trying to
> use Win32 python, not cygwin python.)

Yup.  Once again, the cygcheck output confirmed it:

> $ cygcheck _librsync.dll
> Found: .\_librsync.dll
> .\_librsync.dll
>   C:\cygwin\bin\cygwin1.dll
                  ^^^^^^^^^^^
>     C:\WINNT\System32\KERNEL32.dll
>       C:\WINNT\System32\ntdll.dll
>   C:\cygwin\bin\libpython2.2.dll
                  ^^^^^^^^^^^^^^^^

Thanks,
Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

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