public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Norman Vine" <nhv@cape.com>
To: <cliff@ember.com>, <cygwin@cygwin.com>
Subject: RE: compiling python extensions under Cygwin
Date: Thu, 15 Nov 2001 09:28:00 -0000	[thread overview]
Message-ID: <017601c17440$93f63640$a300a8c0@nhv> (raw)
In-Reply-To: <3BFE32A2.18575.A410FA@localhost>

cliff@ember.com writes:
>
>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?

Well yes, this is windows !

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

Hmm, 

For starters I reccomend using python's Distutils and then building 
extensions should just happen automagically in a cross-platform way.

If you really want to hand build extensions with Makefiles I suggest
downloading the Cygwin Python source distribution and studying 
how it is done there.  

specifically look at the following make defines

CCSHARED
LDSHARED
BLDSHARED

But learn to use the Distutils module, 
it is MUCH simpler once you get the hang of it :-)

Questions about using Distutils should be asked on the Python List

Cheers

Norman


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

WARNING: multiple messages have this Message-ID
From: "Norman Vine" <nhv@cape.com>
To: <cliff@ember.com>, <cygwin@cygwin.com>
Subject: RE: compiling python extensions under Cygwin
Date: Fri, 23 Nov 2001 08:58:00 -0000	[thread overview]
Message-ID: <017601c17440$93f63640$a300a8c0@nhv> (raw)
Message-ID: <20011123085800.xUSvixfHp6vXEBKLrbjjZ88CZ2uF3fKh71mbUqZRK7k@z> (raw)
In-Reply-To: <3BFE32A2.18575.A410FA@localhost>

cliff@ember.com writes:
>
>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?

Well yes, this is windows !

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

Hmm, 

For starters I reccomend using python's Distutils and then building 
extensions should just happen automagically in a cross-platform way.

If you really want to hand build extensions with Makefiles I suggest
downloading the Cygwin Python source distribution and studying 
how it is done there.  

specifically look at the following make defines

CCSHARED
LDSHARED
BLDSHARED

But learn to use the Distutils module, 
it is MUCH simpler once you get the hang of it :-)

Questions about using Distutils should be asked on the Python List

Cheers

Norman


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

  reply	other threads:[~2001-11-23 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15  9:22 cliff
2001-11-15  9:28 ` Norman Vine [this message]
2001-11-23  8:58   ` Norman Vine
2001-11-23  8:29 ` cliff

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='017601c17440$93f63640$a300a8c0@nhv' \
    --to=nhv@cape.com \
    --cc=cliff@ember.com \
    --cc=cygwin@cygwin.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).