Building juju-core on Windows

[John Meinel]

I'm guessing then it is the YAML_STATIC_DECLARE stuff then. On Windows the
default header wants dynamic linking, but then it can't find the _imp_
functions. I thought it needed the lib, but prob it just needed the -D flag.

As for 32 bit, I had some pretty bad experiences with it, but it was all
pre go1.

John
=:->
On Mar 14, 2013 3:09 AM, "David Cheney" <david.cheney at canonical.com> wrote:

> Hmm, that sounds strange, I certainly don't have a libyaml on any of my
> systems, nor do we require it as part of the build recipe. Can you post the
> output of
>
> go build -x launchpad.net/goyaml
>
>
> On 14/03/13 00:48, Gustavo Niemeyer wrote:
>
>> On Wed, Mar 13, 2013 at 9:53 AM, John Arbash Meinel
>> <john at arbash-meinel.com> wrote:
>>
>>> The main blocker is 'goyaml' needing 'libyaml', and using cgo. Which
>>> means we can't just cross-compile, and just downloading and using the
>>> Go binary distribution for Windows isn't quite enough.
>>>
>>
>> I'd have to look at that again for details, but FWIW I already
>> cross-compiled goyaml to Windows before to hand another application to
>> a friend, and I didn't have to fiddle with goyaml.
>>
>>
>> gustavo @ http://niemeyer.net
>>
>>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/**
> mailman/listinfo/juju-dev<https://lists.ubuntu.com/mailman/listinfo/juju-dev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130314/752e996e/attachment.html>