From: Jason Tishler <jason@tishler.net>
To: Charles Wilson <cwilson@ece.gatech.edu>
Cc: "Gerald S. Williams" <gsw@agere.com>, cygwin@cygwin.com
Subject: Re: "Best" way to build a DLL?
Date: Fri, 15 Feb 2002 12:27:00 -0000 [thread overview]
Message-ID: <20020215203224.GO600@hp.com> (raw)
In-Reply-To: <3C6812FF.3020106@ece.gatech.edu>
Chuck,
On Mon, Feb 11, 2002 at 01:52:47PM -0500, Charles Wilson wrote:
> Wrong. Those "warnings" are really just informational messages. The
> python library exports *variables* as well as functions. Your DLL
> probably only exports funtions. DATA exports are very very tricky;
> there is a lot of magic going on to enable Jason to buld python without
> having to use a .def file or __declspec() declarations -- previously,
> these were REQUIRED on exported variables.
Just to be clear, I'm building Cygwin Python the way that I always have
(at least since my shared extension patch was accepted). I assume you
meant that I *could* build without __declspec() declarations if I desired.
Since the __declspec's are there for Win32, I might as well use them.
Now PostgreSQL on the other hand...
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/
next prev parent reply other threads:[~2002-02-15 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 8:24 Gerald S. Williams
2002-02-11 10:44 ` Gerald S. Williams
2002-02-11 10:53 ` Charles Wilson
2002-02-11 10:51 ` Charles Wilson
2002-02-15 12:27 ` Jason Tishler [this message]
2002-02-15 12:52 ` Gerald S. Williams
2002-02-15 13:06 ` Jason Tishler
-- strict thread matches above, loose matches on Subject: below --
2002-02-09 12:55 Nousiainen
2002-02-10 18:34 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020215203224.GO600@hp.com \
--to=jason@tishler.net \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=gsw@agere.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).