macOS M1 building for iOS Simulator, but linking in object file built for iOS, for architecture arm64

[jkelleyrtp]

I can't seem to build for the simulator using the template generated for macOS m1.

I tried to change the x86_64 target to aarch64 but then ran into:

building for iOS Simulator, but linking in object file built for iOS, for architecture arm64

I haven't quite figured out the right way of getting things to build, but at the very least, the template is busted for m1.

As an aside: thank you for doing all this work. It's pretty amazing. Happy holidays!

[woelper]

I noticed a similar error on Intel Mac too, XCode 13.2.1:

  = note: ld: building for iOS Simulator, but linking in .tbd built for macOS/Mac Catalyst, file '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libresolv.tbd' for architecture x86_64
          clang: error: linker command failed with exit code 1 (use -v to see invocation)
          

error: could not compile `myapp` due to previous error
[2022-01-07T13:22:59Z INFO  cargo_mobile::util::cli] exiting with CompileLibFailed(
        CargoBuildFailed(
            Error {
                command: "cargo build --package myapp --manifest-path /Users/johann/repos/myapp/Cargo.toml --target x86_64-apple-ios --color auto",
                cause: CommandFailed(
                    ExitStatus(
                        unix_wait_status(
                            25856,
                        ),
                    ),
                ),
            },
        ),
    )
error: Failed to run `cargo build`

I've tried excluding arm64 on this machine, but with no result. It did work before XCode decided to upgrade to 13.2.1.

This is only on Simulator builds, a normal attached device works fine.

[lucasfernog]

I'm facing an issue that I think might be related.

ld: warning: directory not found for option '-L/Users/project-name/target/x86_64-apple-ios/debug'
ld: library not found for -lproject_name
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I think it should be building arm instead of x86_64, idk what's going on.

[jkelleyrtp]

For anyone following this - I've figured out how to get cargo-mobile working on M1 macs.

#81

I'd be happy to get some help on getting both x86 and aarch64 working in the same fork of cargo-moble.