Skip to content

Conversation

@natario1
Copy link

See discussion: #122 (comment)

To run tests,

  • set either $ANDROID_HOME or multiplatformTesting.androidTools.sdkHome to the Android SDK directory or, if not installed, to some directory where the plugin can download them
  • run ./gradlew atomicfu:runAllAndroidNativeTests

Testing plugin readme: https://github.com/deepmedia/multiplatform-testing/blob/main/readme.md

@mvicsokolova mvicsokolova self-requested a review November 16, 2021 08:42
@natario1
Copy link
Author

natario1 commented Dec 3, 2021

Hi @mvicsokolova , while still hoping that this gets merged soon (I am happy to provide any support)...

Is it OK for you if I publish these artifacts myself in Maven Central, with slightly different coordinates (like my.company.org.jetbrains.kotlinx:atomicfu instead of org.jetbrains.kotlinx:atomicfu)?

The difference would be that my publication would have Android Native targets, while yours hasn't. Then I can do the same for coroutines and write a simple gradle plugin for dependency substitution for end users. From my understanding, the license allows this, but it would be nice to have your approval, even if informally.

@natario1 natario1 changed the title Add androidNative targets + test plugin, bump Gradle to 6.8 Add androidNative targets + test plugin Dec 3, 2021
Copy link

@roy-shchory roy-shchory left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about arm 32 😍

@natario1
Copy link
Author

Arm32 can be added after Kotlin 1.6.20, which contains an important fix for 32bit atomics.

@mvicsokolova
Copy link
Collaborator

We postpone the support of android native targets till the guarantees are published for them.
Please see #122 comment

@qwwdfsad
Copy link
Member

Superseded with #275

@qwwdfsad qwwdfsad closed this Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants