1
0
mirror of https://github.com/golang/go synced 2024-11-19 10:34:46 -07:00
go/misc/ios
David Crawshaw 1fdeb6b58a misc/ios: extra stdout check before run
On one recent job I saw an unexpected SIGSTOP, which I suspect is
simply the job timeout. But the lack of other diagnostics suggests
lldb just didn't see the "run" command.

-----

process handle SIGHUP  --stop false --pass true --notify false
process handle SIGPIPE --stop false --pass true --notify false
process handle SIGUSR1 --stop false --pass true --notify false
process handle SIGSEGV --stop false --pass true --notify false
process handle SIGBUS  --stop false --pass true --notify false
breakpoint set -n getwd
run
(lldb) NAME        PASS   STOP   NOTIFY
==========  =====  =====  ======
SIGHUP      true   false  false
(lldb) NAME        PASS   STOP   NOTIFY
==========  =====  =====  ======
SIGPIPE     true   false  false
(lldb) NAME        PASS   STOP   NOTIFY
==========  =====  =====  ======
SIGUSR1     true   false  false
(lldb) NAME        PASS   STOP   NOTIFY
==========  =====  =====  ======
SIGSEGV     true   false  false
(lldb) NAME        PASS   STOP   NOTIFY
==========  =====  =====  ======
SIGBUS      true   false  false
(lldb) Breakpoint 1: where = libsystem_c.dylib`getwd, address = 0x2f7f7294
(lldb) Process 23755 stopped
* thread #1: tid = 0x104c02, 0x1febb000 dyld`_dyld_start, stop reason = signal SIGSTOP
    frame #0: 0x1febb000 dyld`_dyld_start
dyld`_dyld_start:
-> 0x1febb000:  mov    r8, sp
   0x1febb004:  sub    sp, sp, #0x10
   0x1febb008:  bic    sp, sp, #0x7
   0x1febb00c:  ldr    r3, [pc, #112]            ; _dyld_start + 132
(lldb) go_darwin_arm_exec: timeout (stage br getwd)
FAIL	compress/gzip	359.226s

Change-Id: Ifc2123f5ceaa6d3f9b31bb5cb6e77a2c8ec23818
Reviewed-on: https://go-review.googlesource.com/6613
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
2015-03-03 20:03:32 +00:00
..
clangwrap.sh misc/ios: add README and wrapper script to ease cross-compiling for darwin/arm 2015-02-06 05:50:10 +00:00
go_darwin_arm_exec.go misc/ios: extra stdout check before run 2015-03-03 20:03:32 +00:00
README misc/ios: add README and wrapper script to ease cross-compiling for darwin/arm 2015-02-06 05:50:10 +00:00

Go on iOS
=========

To build a cross compiling toolchain for iOS on OS X, first modify clangwrap.sh
in misc/ios to match your setup. And then run:

	GOARM=7 CGO_ENABLED=1 GOARCH=arm CC_FOR_TARGET=`pwd`/../misc/ios/clangwrap.sh \
	CXX_FOR_TARGET=`pwd`/../misc/ios/clangwrap.sh ./make.bash

To build a program, use the normal go build command:

	CGO_ENABLED=1 GOARCH=arm go build import/path

To run a program on an iDevice, first make sure you have a valid developer
certificate and have setup your iDevice properly to run apps signed by your
developer certificate. Then install https://github.com/phonegap/ios-deploy.
At a first step, you can try building the famous hello world program to run
on your test device.
(The needed files are provided at https://github.com/minux/go-ios-examples.)

	# assume your program binary is helloworld.go, build it into the
	# example hello.app bundle.
	CGO_ENABLED=1 GOARCH=arm go build -o hello.app/hello helloworld.go
	# sign the executable using your developer certificate
	codesign -f -s "iPhone Developer" --entitlements hello.app/Entitlements.plist hello.app/hello
	# run the program inside lldb on iDevice, run `ios-deploy` for more
	# command options
	ios-deploy --debug --uninstall --bundle hello.app
	# Depending on your ios-deploy version, you might need to enter "run"
	# into lldb to run your program, and its output will be shown by lldb.

Notes:
 - A dummy hello.app bundle is provided in this directory to help you get started.
 - Running the program on an iDevice requires code sign and thus external linking,
   if your program uses cgo, then it will automatically use external linking.
   However, if your program does not use cgo, please make sure to add
	import _ "runtime/cgo"
   so that external linking will be used.

Known issues
============
 - crypto/x509 won't build, I don't yet know how to get system root on iOS.
 - Because I still want to be able to do native build, CGO_ENABLED=1 is not the
   default, yet.