x/mobile/cmd/gomobile: bind -target=ios produces an invalid framework #12604
Comments
|
You should be able to build an IPA which depends on the framework without this as well. As far as I can see it is only needed if you attempt to codesign the framework manually. |
|
Correct, its still possible to link against the framework even though it is incomplete. When I brought up this issue, I was actually trying to embed the framework into my binary which was bringing up these errors. That was the incorrect approach to begin with, so I would say this is low priority. However, if you want to make a well formed framework you need to make sure to symlink the Resources folder to the root level and also have an Info.plist in there. But again, its unnecessary if you are just linking against a static framework. |
|
CL https://golang.org/cl/14543 mentions this issue. |
Fixes golang/go#12604. Change-Id: I94e94c32ce42022b58097c349fcbb90edb0a2f13 Reviewed-on: https://go-review.googlesource.com/14543 Reviewed-by: David Crawshaw <crawshaw@golang.org>
Fixes golang/go#12604. Change-Id: I94e94c32ce42022b58097c349fcbb90edb0a2f13 Reviewed-on: https://go-review.googlesource.com/14543 Reviewed-by: David Crawshaw <crawshaw@golang.org>
It results in an error: bundle format unrecognized, invalid, or unsuitable
As s@ pointed out, it's missing info.plist in Resources file.
https://groups.google.com/forum/#!topic/golang-nuts/NqYUz0dq034
We didn't notice this problem because when releasing Ivy, we didn't use the framework - we used the fat .a file and header files directly.
/cc @crawshaw
The text was updated successfully, but these errors were encountered: