Yawning Angel yawn...@schwanenlied.me wrote:
On Mon, 13 Apr 2015 10:14:43 -0400
Nathan Freitas nat...@freitas.net wrote:
One interesting issue is that GoLang 1.4.1, which we are using to
cross-compile the Meek and Obfs4 pluggable transports to Android, only
supports targeting Android ARM
On Mon, Apr 13, 2015, at 02:05 PM, Daniel Martí wrote:
Possibly stupid question, but wouldn't a static linux/x86 binary work
just fine as long as you're executing it directly? As far as I know the
Android port is just for all the bindings involved in e.g. writing a
game in Go that does OpenGL
On Mon, Apr 13, 2015 at 13:09:30 -0400, Nathan Freitas wrote:
One interesting issue is that GoLang 1.4.1, which we are using to
cross-compile the Meek and Obfs4 pluggable transports to Android, only
supports targeting Android ARM for right now... I assume that will
change soon, but if
On Mon, Apr 13, 2015 at 14:30:04 -0400, Nathan Freitas wrote:
We were previously using linux/arm for the PT compiling, and it mostly
worked, but it turns out there are enough small differences in the
Android API from Linux, that it does matter to target Android
specifically. This is similar to
On Mon, Apr 13, 2015, at 12:57 PM, Yawning Angel wrote:
On Mon, 13 Apr 2015 10:14:43 -0400
Nathan Freitas nat...@freitas.net wrote:
One interesting issue is that GoLang 1.4.1, which we are using to
cross-compile the Meek and Obfs4 pluggable transports to Android, only
supports targeting
- Original message -
From: Nathan of Guardian nat...@guardianproject.info
To: guardian-...@lists.mayfirst.org
Subject: Orbot v15 RC3... now with x86/ATOM-power!
Date: Mon, 13 Apr 2015 09:55:44 -0400
Making some tiny changes to external/Makefile and jni/Application.mk
means we can now
On Mon, 13 Apr 2015 10:14:43 -0400
Nathan Freitas nat...@freitas.net wrote:
One interesting issue is that GoLang 1.4.1, which we are using to
cross-compile the Meek and Obfs4 pluggable transports to Android, only
supports targeting Android ARM for right now... I assume that will
change soon,
