Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support iosSimulatorArm64 architecture #77

Closed
kirillzh opened this issue Nov 3, 2022 · 3 comments · Fixed by #108
Closed

Support iosSimulatorArm64 architecture #77

kirillzh opened this issue Nov 3, 2022 · 3 comments · Fixed by #108

Comments

@kirillzh
Copy link

kirillzh commented Nov 3, 2022

Getting this error when targeting iosSimulatorArm64

  > No matching variant of fr.acinq.bitcoin:bitcoin-kmp:0.10.0 was found. The consumer was configured to find a usage of 'kotlin-api' of a library, preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native', attribute 'org.jetbrains.kotlin.native.target' with value 'ios_simulator_arm64' but:
      - Variant 'iosArm64ApiElements-published' capability fr.acinq.bitcoin:bitcoin-kmp:0.10.0 declares a usage of 'kotlin-api' of a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native':
          - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_arm64' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_simulator_arm64'
          - Other compatible attribute:
              - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
@sstone
Copy link
Member

sstone commented Nov 7, 2022

What do you mean by "targeting iosSimulatorArm64" ? How do you trigger this error ? for example are you trying to run tests against an arm64 emulator on a M1 (or M2) machine ?

@kirillzh
Copy link
Author

kirillzh commented Nov 7, 2022

@sstone, that's right, on M1 we need to run an ARM64 simulator, which requires configuring iosSimulatorArm64() target. It is not configured as part of ios() by default (KT-50615), so it needs to be setup manually, for example like so.

@sstone
Copy link
Member

sstone commented Nov 7, 2022

The issue is that we don't provide secp256k1 bindings for macos M1, which is probably what is needed here.
It's a very low priority for us: we don't need it (we can build our iOS app just fine), we would not use it and there is no support yet on github CI (see actions/runner-images#2187 (comment)) or any other CI afaik so we would need to build it manually or host an M1 runner ourselves and we don't want to do that. Of course if github does eventually support macos M1 we will add the missing bindings but I would not hold my breath (the issue above was opened nearly 2 years ago...).

@sstone sstone linked a pull request Jan 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants