On Wed, 15 Dec 2004 22:57:00 +0100, Martin v. Löwis <[EMAIL PROTECTED]> wrote: > Paul Moore wrote: > > For a starter, what steps do you actually take to build a release? I > > assume that the first step is to build Python, by clicking on "build" > > in VS.NET. > > Yes. You can skip this step by just putting all the .pyds, dlls, and > .exes into the PCbuild directory. The packaging will try to pick them > up from there (and proceed if some are missing, like Tcl likely will). > > > Once you have that, is there a single script you run? > > Yes. Invoke Tools\msi\msi.py, using a Python that has pythonwin (i.e. > COM interopability). The only tricky part is that you need cabarc.exe, > which is included in VC, and in the platform SDK.
OK, I've got a copy of the Python sources, and had a look. The change needed to msi.py to include libpythonXX.a in the installer looks simple. But I'm less sure as to where to build the file. It seems to me that msi.py is not the right place - that's focused on building the installer, not building the files to be installed. On the other hand, including it in the build process is a nuisance, as well, as it would add a dependency on mingw (or cygwin) to the MSVC build process. My feeling is that building libpythonXX.a should be a separate step, handled by a dedicated script, which gets run before msi.py. What do others (particularly Martin) think? Should I keep the steps separate, and focused on one task each, or should I incorporate the build of libpythonXX.a into msi.py, so that the installer build still requires just one step? Paul. _______________________________________________ Python-Dev mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
