Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 30 Apr 2001 17:54:09 -0400 From: Jason Tishler To: Mark Hadfield Cc: Norman Vine , Robert Yodlowski , Cygwin Mailing List Subject: Re: Cygwin Python 2.1, Numeric package, exporting init methods Message-ID: <20010430175409.A582@dothill.com> Mail-Followup-To: Mark Hadfield , Norman Vine , Robert Yodlowski , Cygwin Mailing List References: <007c01c0d0fd$ff878a30$d938a8c0 AT Hadfield> <20010430103616 DOT D593 AT dothill DOT com> <005201c0d1be$6ef6bfb0$d938a8c0 AT Hadfield> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="CmigJKgPp1Cv8SBb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <005201c0d1be$6ef6bfb0$d938a8c0@Hadfield>; from m.hadfield@niwa.cri.nz on Tue, May 01, 2001 at 09:42:19AM +1200 Organization: Dot Hill Systems Corp. --CmigJKgPp1Cv8SBb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Mark, On Tue, May 01, 2001 at 09:42:19AM +1200, Mark Hadfield wrote: > From: "Jason Tishler" > > IMO, submitting a patch to the Numpy maintainers using the DL_EXPORT > > macro approach is the way to go. This is the approach that I used > > successfully for numerous standard Python modules. See the following > > for Tim Peters assessment of this approach: > > > > http://mail.python.org/pipermail/python-dev/2001-February/013292.html > > If this is to be the "standard" approach, then that's fine. I guess it > should be documented in "Extending Python"? We really should continue this discussion on the appropriate Python mailing list... > The alternative is changing the compilation & linking process to generate & > use .def files. Norman Vine reported to me yesterday that he could build > Numpy without the DL_EXPORT macros. When we compared notes it turned out > that he was using a modified version of distutils. Basically Norman's > approach is to build with the "cygwin" compiler option: > > python setup.py --compiler=cygwin > > and the distutils patch is attached below my sig. I think it's fairly > self-explanatory. I think that you forgot the attached, but don't worry, I have seen it before. > > Why don't you try the Numpy maintainers and see what they have to say? > > Since they already support a Win32 port, I can't imagine much resistance > > on their part. > > I'd be glad to do that but first I would like a ruling from the > Cygwin-Python gods about which of these approaches is the > one-true-Pythonic-way. I have attempted to pursue this approach -- see the attached for details. Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason DOT Tishler AT dothill DOT com Hazlet, NJ 07730 USA WWW: http://www.dothill.com --CmigJKgPp1Cv8SBb Content-Type: message/rfc822 Content-Disposition: inline Date: Mon, 30 Apr 2001 12:46:18 -0400 From: Jason Tishler To: Norman Vine Bcc: jt+misc DOT copy AT ny DOT dothill DOT com Subject: Re: Cygwin Python 2.1, Numeric package, exporting init methods Message-ID: <20010430124618 DOT G593 AT dothill DOT com> References: <20010430103616 DOT D593 AT dothill DOT com> <002801c0d188$bf21e180$a300a8c0 AT nhv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002801c0d188$bf21e180$a300a8c0 AT nhv>; from nhv AT cape DOT com on Mon, Apr 30, 2001 at 11:18:00AM -0400 Organization: Dot Hill Systems Corp. Norman, On Mon, Apr 30, 2001 at 11:18:00AM -0400, Norman Vine wrote: > In trying to get Mark up and running I noticed that Numerical > compiled out of the box for me because I still had some of a > patch that I believe MA Lenburg submitted that was not > in his patch after it was rewritten on submission > > I have attached my diffs > > Any thoughts on my resubmitting these ? > They seem to work for me and do not require the DL_EXPORT > MACRO discussed below. < confirmed by Mark in private email > I attempted to pursue the above in the following: http://mail.python.org/pipermail/distutils-sig/2001-February/002003.html but I didn't receive any responses so I dropped it. I'm sorry but I don't have the cycles to pursue this myself. I still think that the DL_EXPORT approach is the way to go. Of course, you are welcome to spear head this effort yourself. Remember to wear your helmet... :,) Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason DOT Tishler AT dothill DOT com Hazlet, NJ 07730 USA WWW: http://www.dothill.com --CmigJKgPp1Cv8SBb Content-Type: text/plain; charset=us-ascii -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple --CmigJKgPp1Cv8SBb--