bzr-windows team mailing list archive

[Maritza Mendez <martitzam@xxxxxxxxx>]

On Mon, Oct 11, 2010 at 11:40 AM, Gary van der Merwe <garyvdm@xxxxxxxxx>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/10/2010 19:39, Maritza Mendez wrote:
> > Right!  It looks like the Windows builds are currently being done with
> > the free VS2008 and in the EC2 cloud.  This adds complexity to what is
> > already a pretty complicated build, even for x32.  I'm in the process
> > (slow, in my spare time) of getting the x32 build going (on my own
> > hardware and retail VS2008) with the plan being to then move on to x64.
>
> Correction: The ec2 build host has the paid for version of vs.
>
> Correction noted.  Thanks.



>
> > Question: Does the Windows package of bzr really need to support more
> > than one version of python?  I'm inclined to build bzr+friends for
> > python 2.6 or 2.7 and drop the legacy.  I especially want to drop
> > MinGW.  I have the 32- and 64-bit MinGW compilers both working, but
> > again it's extra work which does not seem to add value now that we have
> > python 2.6 which I gather is built using VS200x anyway.
>
>
> We build python installers for different versions, but these just
> install site-packages in an existing python installation, and so the
> architecture support is base on the python installation that you install
> into.
>
> Thanks for clarifying that.



> These python installers are really easy to get building. The thing that
> makes it difficult so build the stand alone py2exe installer, with all
> the plugins, is tortoisebzr. It would be great to make it possible to
> disable building components (such as tortoisebzr, or the python
> installers.)
>
>
I must admit my bias: I am most interested in getting a 64-bit build of
pyrex bits to finally get around the "2GB limit."   Other components like
tbzr are not part of my primary objective.


> I started building my own 32bit build host, with the free beer version
> of vs.  I got stuck getting the 64bit tortoisebzr shell extension to
> build. According to the link bellow, this is a bit more tricky with the
> free beer version if vs. As you have the paid for version, it should be
> a bit easier for you.
>
>
> http://jenshuebel.wordpress.com/2009/02/12/visual-c-2008-express-edition-and-64-bit-targets/
>
> Thanks for the link.  I think you're right: the retail version should have
fewer of these issues.



> While trying to build my own build host, I started updating the
> oc/developers/win32_build_setup.txt doc. I've not merged it in to
> bzr.dev, cause I was going to wait till I get it working, but you may
> find it useful, so I've pushed it here: lp:~garyvdm/bzr/win_build_doc
>
> Thanks!  That doc was showing some age.  I will definitely read your
notes.

~M