bzr-windows team mailing list archive

[Maritza Mendez <martitzam@xxxxxxxxx>]

John... You might well be clever enough to trick msvc into linking
with older runtime libs.  But there are only tears on that path.  I
have learned this the hard way.  When ms tells you which way to go
with their tools it is wise to follow.

-M


On 8/11/09, John Arbash Meinel <john@xxxxxxxxxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alexander Belchenko wrote:
>> John Arbash Meinel пишет:
>>> Alexander Belchenko wrote:
>>>> Ian Clatworthy пишет:
>>>>> Assuming everyone who wanted to voice an opinion on what installers are
>>>>> required has done so, the time has come IMO for some follow-up action.
>>>>> Here are the next steps I'd like to see happen:
>>>>>
>>>>> 1. Someone volunteers to summarise the consensus and list any
>>>>>    outstanding issues to be decided or further investigated.
>>>> I have troubles to see consensus, but Ian said there should be one.
>>>> So I'll try to list replies.
>>>>
>>
>>>> f) x64 support: require Python 2.6 as strong dependency. But x86
>>>> (32-bit) works just fine on Python 2.5. What is idea? Push bzr.exe to
>>>> use Python 2.6? It will definitely require MSVC 2008 to build C
>>>> extensions, I don't know is MinGW can link against newer run time libs.
>>>> Somebody should test to build bzr C extensions either with MinGW + Py
>>>> 2.6 or with MSVC Express Edition. (But TBZR anyway require MSVC 2008
>>>> full edition). Separate installers for x86 and x64 or put everything
>>>> together?
>>>
>>> We can, and do, build the windows extensions using MinGW for python2.6.
>>> It seems it is only Microsoft compilers that have trouble compiling
>>> against different versions of the Microsoft runtime... :)
>>
>> Well, I hope everything is OK then. In the past I've told that C
>> extension should be linked against exactly the same msvcrt library that
>> Python is built otherwise there is possible very bad runtime crashes
>> when manipulation with OS file handles are performed. Maybe this sort of
>> issues is not the problem for bzr.
>>
>>
>
> That is very true. The main thing is that Mingw has figured out how to
> do this. (Or at least always links against a really old version that is
> known to be available.) I haven't yet figured out a way to tell Visual
> Studio 2008 to build against the 2003 libraries. (For python <= 2.5)
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqBfgIACgkQJdeBCYSNAAO32ACeIR44OX/9cPJYQVWU5jVpLZXz
> QXUAnRMzv0ie30pfGhTDqTCkCmjBecZz
> =YCe1
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Mailing list: https://launchpad.net/~bzr-windows
> Post to     : bzr-windows@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~bzr-windows
> More help   : https://help.launchpad.net/ListHelp
>