Home Original page

Compiling Python on Win32

Kevin F. Smith smithkf at OMIT_THIS.us.ibm.com
Fri Oct 13 19:46:36 EDT 2000 
I'm trying to add an import-able module to python on Windows NT.  I am
using MS VC++ 5.0 (Dev Studio 97), and the Workspace file that comes
with the Python source code seems to work great (i.e., pcbuild.dsw)

Then to add the module that I am trying to add, I used the same
workspace (i.e., pcbuild.dsw), and went to the "python15 files" section
and added the module name (e.g., xmodule.c).  Then doing a build of both
the python15 files and the python files seems to result in a good .exe
and .dll.  I seem to be able to do everything except for "import x",
which gives: No Module named x.  All of the other modules seem to import
just fine.

To make sure that I am getting the modules from the new compile, I added
a printf() statement inside of the init function of one of the standard
modules, and sure enough, it prints the message when I import that
module, so I'm obviously running the newly compiled version of python.

What do I need to do to get the newly created module to also show up
when I try and import it?

On AIX, using ./configure and make, everything seems to work.  But there
must be something simple that I am missing on MS VC++ 5.0.

Thanks for any suggestions!
--kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20001013/dc53f248/attachment.html>
More information about the Python-list mailing list