[python-win32] building pywin32 on Server 2003 x64

[Hanni Ali]

Thanks for some of the advice,

A little background so my questions make sense.

This deployment is for a mission critical application. I am migrating it
from python-2.4 to 2.5 also changing the code which uses numarray/numeric to
use numpy which is one of the main parts of the move (I thought), this is
necessary as python > 2.5 uses numpy instead. This also should allow us to
manipulate objects over 2GB, I believe this would only be on 64bit platforms
though hence my need for 64 bit.

Firstly, I am currently using VS2005 as I am compiling Python-2.5.2 because
I was going for the most stable python. Everyone here seems to think I
should be using 2.6, as far as I can tell this is still in alpha and I am
not convinced of the wisdom of using an alpha testing system for production.
Secondly we don't have 2008 yet in my organisation and the express edition
doesn't contain the 64 bit compiler.

All my development is on a 64bit system (I am not cross compiling). I have
been using the SDK for server 2003. If I manage to sort this out anything I
have I will be sure to share. However although I have managed to coax
subversion to download through our firewall I have not yet managed to get
CVS to do so and have been downloading CVS at home on my linux machine and
e-mailing it in (not ideal!).

What do people think of python 2.6 on windows? is it ready? I note the first
beta should be out on the 4th June, this might be more reasonable. I don't
think I could sell "let's use this alpha version in production" to anyone ;)

Thanks,

Hanni




2008/5/31 Mark Hammond <mhammond at skippinet.com.au>:

>  There is a buglet in bdist_wininst and --skip-build - note that the
> filename created by your process doesn't have "py2.6" included in the
> filename.  To fix that, the final command should also include
> "--target-version=2.6"
>
>
>
> Cheers,
>
>
>
> Mark
>
>
>
> *From:* Marc-André Belzile [mailto:mbelzile at softimage.com]
> *Sent:* Saturday, 31 May 2008 1:03 PM
> *To:* Mark Hammond; Hanni Ali; python-win32 at python.org
> *Subject:* RE: [python-win32] building pywin32 on Server 2003 x64
>
>
>
> Meanwhile, if you're still up to the challenge, here are the steps I used
> for building pywin32 for vista 64:
>
>
>
> 1) svn co http://svn.python.org/projects/python/trunk python
> 2) compile python 2.6 for x64 from VS2008 IDE or Windows SDK
> 3) open x64 command-prompt
> 4) log as anonymous to pywin32 server: cvs
> -d:pserver:anonymous at pywin32.cvs.sourceforge.net:/cvsroot/pywin32 login
> 5) download latest pywin32 source: cvs -z3
> -d:pserver:anonymous at pywin32.cvs.sourceforge.net:/cvsroot/pywin32 co -P
> pywin32
> 6) c:\dev\pywin32>\build ..\python2.6\python\PCbuild\python.exe setup.py
> build --plat-name=win-amd64
> 7) c:\dev\pywin32>\build ..\python2.6\python\PCbuild\python.exe setup.py
> bdist_wininst --skip-build
>
>
> The pywin32 install package should be generated here
> c:\dev\pywin32>\build\dist\pywin32-210.9.win32.exe
>
>
>
> Hope that helps
>
>
>
> -mab
>
>
>
>
>  ------------------------------
>
> *From:* python-win32-bounces at python.org [mailto:
> python-win32-bounces at python.org] *On Behalf Of *Mark Hammond
> *Sent:* May-30-08 6:38 PM
> *To:* 'Hanni Ali'; python-win32 at python.org
> *Subject:* Re: [python-win32] building pywin32 on Server 2003 x64
>
> pywin32 builds on a 64bit environment, but you need the SVN trunk of
> Python, the CVS trunk of pywin32, and VS2008.  VS2005 support isn't *that*
> interesting to me as there are no Python binaries available built with that
> compiler and I can't get VS.NET to build with the most recent Vista SDK,
> which is needed for recent pywin32 functionality.  A Python 2.6 amd64 build
> will be included in the next release.
>
>
>
> Cheers,
>
>
>
> Mark
>
>
>
> *From:* python-win32-bounces at python.org [mailto:
> python-win32-bounces at python.org] *On Behalf Of *Hanni Ali
> *Sent:* Friday, 30 May 2008 11:00 PM
> *To:* python-win32 at python.org
> *Subject:* [python-win32] building pywin32 on Server 2003 x64
>
>
>
> Hi All,
>
>
>
> I am attempting to build pywin32 for a 64 bit deployment.
>
>
>
> It is necessary for us to use 64 bit python due to objects within our
> application exceeding 2GB in size.
>
>
>
> I am attempting to do so using msvc 2005 which I know is not ideal, but I
> have managed to build the other dependencies (Python, numpy), my attention
> is now on pywin32.
>
>
>
> Firstly although I have managed to get it compiling, I was not able to use
> the instruction:
>
>
>
> setup.py build --plat-name=win-amd64
>
>
>
> The setup script reported plat-name as not existing.
>
>
>
> Secondly is anyone building pywin32 on 64 bit machines?
>
>
>
> Although I seem to have hacked it suficiently to get it to compile linking
> fails with errors of this manner:
>
>
>
> MSVCRT.lib(gs_support.obj) : error LNK2019: unresolved external symbol
> __imp_Get
> CurrentThreadId referenced in function __security_init_cookie
>
>
>
> I appreciate any help anyone can give.
>
>
>
> Thanks
>
>
>
> Hanni
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-win32/attachments/20080531/ad0ae83a/attachment.htm>