gx support ( for IPFS )

[karalabe]

gx support ( for IPFS )

[karalabe]

@lgierth @ligi If you specify a full import path, xgo will try to download it and all deps from the internet. The reason behind this decision was to allow reproducible builds that are not sensitive on some local dependency having a different version, causing weird failures.

However, xgo does have support for building local stuff, but it has to be pointed to it using a relative or absolute path, not an import path.

If the path is not a canonical import path, but rather a local path (starts with a dot . or a dash /), xgo will use the local GOPATH contents for the cross compilation.

$ mkdir /tmp/workspace
$ cd /tmp/workspace/
$ export GOPATH=/tmp/workspace/
$ export PATH=$GOPATH/bin:$PATH
$ go get -d github.com/ipfs/go-ipfs
$ cd $GOPATH/src/github.com/ipfs/go-ipfs
$ make toolkit_upgrade
$ make deps
$ xgo --targets=android-23/* ./cmd/ipfs

$ ls -al
-rwxr-xr-x  1 root     root     27820792 May  3 14:43 ipfs-android-23-386
drwxr-xr-x  3 root     root         4096 May  3 14:44 ipfs-android-23-aar
-rwxr-xr-x  1 root     root     27458756 May  3 14:42 ipfs-android-23-arm
-rwxr-xr-x  1 root     root     36925472 May  3 14:44 ipfs-android-23-arm64

@ligi did you make deps?

@karalabe I'm wildly guessing because I've never used xgo -- does it respect GOPATH? The output looks like it downloads its own copy of the package(s), which breaks gx's non-go-get package management.

@whyrusleeping have a look -- this might be solved by gx-go rewrite --undo.

[ligi]

@karalabe thanks for the info & your work! Closing this issue then as this seems to be a feature and no bug

Ah yes that makes a lot of sense, thanks @karalabe