[go-nuts] Re: x/mobile: Feature, add "-target=io/arm,ios/386" and "-nobitcode" to bind command

s target. for architecture arm64 > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > Which indicates the generated framework does not contain bitcode. > > Ho to get the bitcode generated? > > On Monday, April 1, 2019 at 9:30:23 AM UTC-7, Tr

[go-nuts] Re: x/mobile: Feature, add "-target=io/arm,ios/386" and "-nobitcode" to bind command

onday, April 1, 2019 at 12:09:35 AM UTC-7, ma...@eliasnaur.com wrote: > > Hi, > > The -target flag does support architectures. Have you tried -target > ios/amd64,ios/arm64,ios/arm from your example? > > I'm not sure I understand the problem with bitcode and macOS; what is

[go-nuts] x/mobile: Feature, add "-target=io/arm,ios/386" and "-nobitcode" to bind command

Hi! First, gomobile has been a real life saver thank you to all of those who have contributed. The current commit at master (167ebed0ec6dd457a6b24a4f61db913f0af11f70) automatically adds the "-fembed-bitcode" flag to the cflags and it also automatically builds for all of iOS architectures. We

[go-nuts] Re: gomobile init should have a flag if we want only IOS or Android

I feel that it would be useful, a while ago we were only doing Android Go/mobile development and it forced the iOS download; consider opening an issue here: https://github.com/golang/go/issues On Monday, August 29, 2016 at 7:22:14 AM UTC-7, Abhishek Sinha wrote: > > While doing gomobile init on O