On 31 Mar, 00:32, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote:
> En Sun, 30 Mar 2008 12:04:10 -0300, axl <[EMAIL PROTECTED]>
> escribió:
>
> Which changes are those? I can build Python straight from the svn sources.
I upgraded the project files to VS2008 format, changed some obsolete
settings,
En Sun, 30 Mar 2008 12:04:10 -0300, axl <[EMAIL PROTECTED]>
escribió:
> I'm going to be adding some features for a python-project with
> external modules written in C. However, if I build modules with my
> MSVS 2008 compiler (from the Windows SDK), they won't load in Python
> 2.5.2, which is bui
On 30 Mar, 17:40, "Ryan Ginstrom" <[EMAIL PROTECTED]> wrote:
> Another option is to compile your extensions with gcc, and specify that it
> link to MSVCR71.dll as the C runtime.
>
> For MinGW, it's sufficient to edit the specs (e.g. in
> C:\MinGW\lib\gcc\mingw32\3.4.2) like so:
> *libgcc:
> %{mthre
> On Behalf Of axl
> Since I don't have access to MSVS 2003 I need to rebuild
> Python using MSVS 2008 in order for the binaries to go along.
Another option is to compile your extensions with gcc, and specify that it
link to MSVCR71.dll as the C runtime.
For MinGW, it's sufficient to edit the sp
Hi,
I'm going to be adding some features for a python-project with
external modules written in C. However, if I build modules with my
MSVS 2008 compiler (from the Windows SDK), they won't load in Python
2.5.2, which is built with MSVS 2003.
Since I don't have access to MSVS 2003 I need to rebuild
