[jira] [Commented] (PROTON-1034) [Go binding] Windows build fails if Go language is installed but no gcc tool kit

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PROTON-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985529#comment-14985529 ] 

ASF subversion and git services commented on PROTON-1034:
---------------------------------------------------------

Commit 288070d8e4856bc7664270cb5ca51ebaa22b8efc in qpid-proton's branch refs/heads/master from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=288070d ]

PROTON-1034: Go binding on Windows defaults to Off


> [Go binding] Windows build fails if Go language is installed but no gcc tool kit
> --------------------------------------------------------------------------------
>
>                 Key: PROTON-1034
>                 URL: https://issues.apache.org/jira/browse/PROTON-1034
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: go-binding
>    Affects Versions: 0.11
>         Environment: Windows with Go but without CYGWIN gcc.
>            Reporter: Chuck Rolke
>            Assignee: Chuck Rolke
>
> Go builds detect the presence of the Go executable and build based on that.
> On Windows the build also requires gcc/ld which are part of a separate tool kit such MINGW or CYGWIN. Even then there are issues with
> * the debug postfix 'd' character on library names
> * 32-bit/64-bit library detection
> The proton-c builds should still work even if Go is installed. This issue tracks solving the build problem by defaulting the Go binding to OFF on windows. Users with or without Go installed will still get a good proton build but with no Go binding. A developer can issue -DBUILD_GO=Yes to force the build while he works out the gcc interface issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)