Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Mon, 13 May 2002 11:51:42 -0400 From: Jason Tishler Subject: Re: Cygwin Python with a static Python library? In-reply-to: <127216591702.20020511234429@familiehaase.de> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20020513155141.GC1408@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: <20020508115001 DOT GA1700 AT tishler DOT net> <127216591702 DOT 20020511234429 AT familiehaase DOT de> Gerrit, On Sat, May 11, 2002 at 11:44:29PM +0200, Gerrit P. Haase wrote: > 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...? Not much, but now you have one less DLL as a dependency. It appears to make people "freezing" Python scripts (into executables) happy. :,) > Anyway, who wants to get a static libperl just needs to rebuild perl > and there it is. Unfortunately, Python with a static libpython needs some help during the build process. This issue has just become visible now that Python has a "--disable-shared" configure option. I have submitted a patch (which has been accepted) to default to "--enable-shared" under Cygwin. I currently have no plans to submit a patch to enable clean building of Cygwin Python when configured with "--disable-shared". Jason -- 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/