Building juju-core on Windows

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-03-13 18:44, Martin Packman wrote:
> On 13/03/2013, John Arbash Meinel <john at arbash-meinel.com> wrote:
>> 
>> Short summary, I can get a custom compiled 32-bit go tools using 
>> mingw. Compile libyaml, tweak goyaml and get 'go test' to pass
>> for goyaml. I made some progress in getting 64-bit tools working,
>> but I'm currently blocked on getting 64-bit libpthread.
> 
> Good progress. Do we actually care about providing a 64-bit
> windows client? It seems from the golang docs ("64-bit Theory")
> that it's not a polished process, and a 32-bit binary should work
> for everyone, no?

Well the tools I got from golang.org were 64-bit binaries. And I know
in the past go's support for 32-bit was pretty poor. (The memory
allocator has a hard time freeing memory that isn't referenced because
the pointer values aren't as unique.)

Certainly I would say we don't need >2GB of memory for Juju, but the
general go tool support seems better for 64-bit.

> 
>> 7) On Windows, 'strdup' is available as '_strdup', so you need a 
>> workaround like: +#ifdef WIN32 +#define strdup _strdup +#endif
>> 
>> There are a lot more funcs like this, but goyaml isn't calling
>> them directly.
> 
> Should be able to just define _CRT_NONSTDC_NO_DEPRECATE for this:
> 
> <http://msdn.microsoft.com/library/ms235384>
> 
> Martin
> 

Thanks. I can certainly set that at a build level.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFAlC0ACgkQJdeBCYSNAAOJ1ACfVuwrypt2qfxdqj8/DryyJZLN
o6oAmwSaT/X6lu5L8tzpNU9/E+KcIBtS
=lik2
-----END PGP SIGNATURE-----