> Lo and behold! --
>
> Performing Custom Build Step
> '.\make_versioninfo.exe' is not recognized as an internal or external
> command,
> operable program or batch file.
> Project : error PRJ0019: A tool returned an error code from
> "Performing Custom Build Step"
Hmm. make_versioninfo.exe should
On Nov 21, 3:50 pm, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > I need to compile that module for that release and platform, but I
> > have been unable to discover which MS compiler version and runtime was
> > used to generate the binaries. My understanding is that Python 2.5.2
> > in gener
On Nov 21, 3:50 pm, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > I need to compile that module for that release and platform, but I
> > have been unable to discover which MS compiler version and runtime was
> > used to generate the binaries. My understanding is that Python 2.5.2
> > in gener
> I need to compile that module for that release and platform, but I
> have been unable to discover which MS compiler version and runtime was
> used to generate the binaries. My understanding is that Python 2.5.2
> in general uses Visual Studio 2003, but MS does not appear to have
> shipped an I
Hello,
A tool that we use needs to be ported to Itanium. It wsa written
for Python 2.5.2, and so I was happily using the Itanium version of
that release. However, as I have gotten deeper into the port, I see
that ctypes was not included with the Itanium Python 2.5.2 release.
I need to compi
