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: Sat, 11 May 2002 23:44:29 +0200
From: "Gerrit P. Haase" <gp AT familiehaase DOT de>
Reply-To: "Gerrit P. Haase" <gp AT familiehaase DOT de>
Organization: Esse keine toten Tiere
X-Priority: 3 (Normal)
Message-ID: <127216591702.20020511234429@familiehaase.de>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin Python with a static Python library?
In-Reply-To: <20020508115001.GA1700@tishler.net>
References: <20020508115001 DOT GA1700 AT tishler DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hallo Jason,

Am Mittwoch, 8. Mai 2002 um 13:50 schriebst du:

> There have been some recent posts on python-list@ regarding whether
> or not Cygwin Python should be built with a shared (i.e., DLL) Python
> library or a static one.  Note that Cygwin Python currently uses a DLL
> library like the Win32 one.

> Does anyone have compelling reasons why Cygwin Python needs a static
> library?  If so, then I will consider submitting a patch to Python CVS
> to enable this for Cygwin.  Unfortunately, it will be difficult to fit
> this cleanly into the Python Unix build infrastructure due to the extra
> steps required to build an executable that exports symbols with the
> current Cygwin binutils.

Perl builds a static version of libperl for bootstrapping, but it gets
not installed.  I think that it is not needed (well I have no idea for
what I should use it).

> See attached for more details, if interested.

That is interesting.  miniperl is not able to load dynamic modules.

=
Can't load module IO, dynamic loading not available in this perl.
  (You may need to build a new perl executable which either supports
  dynamic loading or has the IO module statically linked into it.)
=

Now I think:  What is the difference, to link against a .dll which
exports the symbols or link against an executable which exports
the symbols...?

Anyway, who wants to get a static libperl just needs to rebuild perl
and there it is.


Gerrit
-- 
=^..^=


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