Mark:<br> Where can one find a cookbook for HOW to build python and/or pywin32 from source? I guessed that one should use VS 2003 (which I have) but I have no clue how to make it actually compile. Someone mentioned a patch to compile using a later (2005?) version of Visual Studio. I really want to try with VS 2008 express, so that I can work on my home machine, rather than the one at work where we have the licen$ed version, but the first step is to make it work with the supported environment. Where do I look for documentation?<br>
--<br>Vernon Cole<br><br><div class="gmail_quote">On Mon, Jan 28, 2008 at 5:28 PM, Mark Hammond <<a href="mailto:mhammond@skippinet.com.au">mhammond@skippinet.com.au</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">TimR wrote:<br>
<br>
> You need to set the Python path variable before calling the<br>
> interpreter. You can do that by setting the PYTHONPATH environment<br>
> variable, but I believe you can also do that by setting variables when<br>
> you initialize the interpreter.<br>
<br>
</div>Actually, if the 'lib' directory can be found relative to pythonxx.dll, it<br>
should not be necessary to set PYTHONPATH at all. Even then, if it *was*<br>
necessary to set such a variable, it may be better to set PYTHONHOME instead<br>
- that should adjust PYTHONPATH (again, the lib can be located relative to<br>
that dir), along with ensuring sys.prefix etc are all correct, thereby<br>
allowing things like distutils to do the right thing.<br>
<div class="Ih2E3d"><br>
> Py2exe might prove useful for you, if only because it scans through a<br>
> Python script and determines exactly which auxiliary DLLs and modules<br>
> the script needs in order to operate in a standalone environment.<br>
><br>
> > Also, our application is built with VS 2005, should Python also be<br>
> > built with the same VS version for compatibility?<br>
> ><br>
><br>
> Yes, this is required. The Python run-time DLL links to the Visual C++<br>
> run-time library. My python24.dll, for example, links to msvcr71.dll,<br>
> which is the run-time from VS 2003.<br>
<br>
</div>On the other hand, it would work fine if you built Python and all modules<br>
with the same compiler. You can not *mix* compilers, but using a<br>
non-default one should work fine so long as you control every binary you<br>
load. That is a burden though.<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Mark<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
python-win32 mailing list<br>
<a href="mailto:python-win32@python.org">python-win32@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-win32" target="_blank">http://mail.python.org/mailman/listinfo/python-win32</a><br>
</div></div></blockquote></div><br>