public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* compiling python extensions under Cygwin
@ 2001-11-15  9:22 cliff
  2001-11-15  9:28 ` Norman Vine
  2001-11-23  8:29 ` cliff
  0 siblings, 2 replies; 4+ messages in thread
From: cliff @ 2001-11-15  9:22 UTC (permalink / raw)
  To: cygwin

Hi--

I'm trying to move some python extensions from Linux to Cygwin, 
and I don't know how to compile them properly.  Searching the web 
didn't yield much info, so any examples/howtos would be greatly 
appreciated.

Specific questions:

1.  Cygwin python (2.1.1) doesn't seem to import ".so" files, so I 
assume that I must compile to ".dll"  Could someone confirm this?
Are there alternatives?

2.  When I try to create a ".dll" using the information on the Cygwin 
website, I get a linker warning saying that it could not find a 
reference to mainCRTStartup (even though my extension does not 
have any GUI).  Importing the resulting .dll leads to a segfault.  
What gives?

Thanks for reading this far and for any pointers to resources on the 
web or in print.

--Cliff




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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2001-11-23 16:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-11-15  9:22 compiling python extensions under Cygwin cliff
2001-11-15  9:28 ` Norman Vine
2001-11-23  8:58   ` Norman Vine
2001-11-23  8:29 ` cliff

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).