Thanks for your message Matthieu
I agree that would give me a build but I'd rather have Numpy and Scipy
source codesets each in their own
workspaces so that as we try to port across to PharLap we have full
visibility.
I wonder if anyone has done similar in visual studio 2003 or higher?
I'm runnin
2008/9/17 Richie <[EMAIL PROTECTED]>:
> Hello
>
> I wonder if anyone can advise me or has done similar to the
> following?
>
> Basically I've downloaded the Python 2.5.2 source code that builds
> with Visual Studio 6.0. I've built Python for windows. This was easy
> (it even came with the pcbuild.d
Hello
I wonder if anyone can advise me or has done similar to the
following?
Basically I've downloaded the Python 2.5.2 source code that builds
with Visual Studio 6.0. I've built Python for windows. This was easy
(it even came with the pcbuild.dsw workspace file). Great!
Now comes the troubled b
