rive-app / rive-app/rive-runtime

Feature request: Upload rebuilt static libraries with each release

Open
#69 0 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
C++
Stars
1.2k
Forks
121
PR merge metrics
No merged PRs in 30d

Description

It would be nice if each release would also upload prebuilt libraries for all targets.
This would save developer a lot of headache in trying to install all the sdk's locally themselves.

Some notes

No external libraries

The developer needs to be in as much control as possible in choosing exact versions to include, as long as they're ABI compatible.
E.g. the goal is to only include one libharfbuzz.a in the build.

Instead, make a note in the uploaded Readme.md which versions of the external libraries are used. E.g. Harfbuzz 11.2.1 to let the developer sort it out.

Target as old Android NDK/version as possible

Making sure that the developer can target lower end devices is good in order to reach as many users as possible.
Alternatively, upload multiple versions of the library.

iOS

Making sure the iPhoneSimulator target is added to the list of architectures.

Exposing the minimum target version. We use 11.0, but rive has 13.0 hardcoded.
Similarly we use osx min version 10.15, and rive has 11.0 hardcoded.

The list of architectures

To give a glimpse of what architectures are currently built for each release

  • x86-win32
  • x86_64-win32
  • arm64-linux
  • x86_64-linux
  • arm64-macos
  • x86_64-macos
  • arm64-ios
  • x86_64-iosimulator
  • arm64-android
  • js-web
  • wasm-web
  • wasm_pthread-web

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by mapping the existing release build process to the listed architectures and determining how artifacts are currently produced. Done means each release publishes the requested static libraries without bundled external libraries, documents dependency versions and minimum targets in Readme.md, and includes the requested simulator architecture.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp, ios
Domain
build-system, mobile-dev, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.