liveview-native / liveview-native/liveview-native-core

Generate library for host machines

Open
#107 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
166
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Currently, the [LVN Client Jetpack](https://github.com/liveview-native/liveview-client-jetpack) library relies on Core Jetpack and it's working fine on Android devices.
However, to run unit tests (particularly the Screen Shot tests)of the LVN Client Jetpack, it's necessary to have a version of the Core Jetpack compiled to host architectures like Windows, Linux, and Mac OS.

At the moment, what I did was:
- added the "darwin-aarch64" target (because I'm using a M1 Macbook);
- ran the command `./gradlew assembleRelease` to generated the `*.dylib` file;
- copied the binary to the `liveview-android/src/test/jniLibs` directory in the LVN Client Jetpack project.

The ideal solution would be to release a dependency just for unit tests and declare it in the `dependencies` section like:
```
testImplementation "com.github.liveview-native:liveview-native-core-jetpack-host:"
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the host target configuration and the ./gradlew assembleRelease entry point; the issue specifically mentions adding the darwin-aarch64 target and generating a .dylib. Compare that output with the liveview-android/src/test/jniLibs usage and the proposed testImplementation dependency. Done means host builds for Windows, Linux, and macOS can be consumed by LVN Client Jetpack unit tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
build-system, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.