Giovanni Bajo wrote: > Thomas Heller <[EMAIL PROTECTED]> wrote: > >> Missing are .vcproj files for Windows, both for the _ctypes.pyd extension >> and the _ctypes_test.pyd extension needed for testing. IIRC, Martin >> promised to create them - is this offer still valid? I could do that >> myself, but only for x86, while other .pyd files also have build settings >> for Itanium and x86_64. (I find it always very painful to click through >> the settings dialog in MSVC - isn't there any other way to create these >> files?) > > > I discussed with Martin a bit about the opportunity of generating .vcproj > files with a script-driven tool. I'm going to try and setup something as > soon as I find some spare time. > > The goal of this work would exactly fit your need: make the creation of > extension modules trivially easy (just as easy as adding the modules to the > main python.dll). My personal goal, in fact, is to move many of those > builtin extension modules from python.dll out into their own .pyd files > where they'd belong (were not for this technical annoyance of being forced > to use the settings dialog in MSVC).
Ideally this would be integrated with distutils because the setup-script has most of the information that's needed. OTOH, extensions could be built with distutils even for core Python, and even on Windows. For extensions that are *not* builtin or not included with Python itself distutils works good enough. Oh, IIRC the pywin32 setup script has code that is able to parse MSVC6 project files and create a distutils Extension instance from them - maybe this can help you. Thomas _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
