Gerald,
On Fri, Feb 15, 2002 at 03:52:28PM -0500, Gerald S. Williams wrote:
> Presumably, the distutils package sets this automatically, ...
Yes it does.
Jason
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation:
Thanks for the nudge. After seeing your mail, I poked around
pyconfig.h and found the USE_DL_IMPORT define.
Anyway, if you're linking to Cygwin Python, -DUSE_DL_IMPORT
on the gcc line eliminates those informational "Warnings",
at least from the Python library. Presumably, the distutils
package se
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
Take a look at the new examples in the dllhelpers. I've added four new
examples for building DLLs using libtool and friends.
--Chuck
Nousiainen wrote:
> This seems to be the most complicated thing .. building a DLL file. So,
> what is the best and recommended way to do the job using recent
This seems to be the most complicated thing .. building a DLL file.
So, what is the best and recommended way to do the job using recent cygwin tools?
I've read autobook (http://sources.redhat.com/autobook/autobook/autobook_toc.html) and
it gives some good advice (I'm using autotools in my projec
5 matches
Mail list logo
