Uniwind pro build step is load-intensive

[antoinerousseau]

What happened?

When the app is building locally, the Android Uniwind build step (CMake etc) is slow and also makes my computer almost unusable (even though it's a M2 Pro MacBook Pro...)

In the CI, the app build is significantly slower since we added Uniwind Pro (Android build went from 20 minutes to 30 minutes).

Any way you could provide pre-built binaries? Like it's done at https://rnrepo.org/

Steps to Reproduce

1. Install Uniwind Pro
2. expo prebuild
3. expo run:android

Snack or Repository Link (Optional)

No response

Uniwind version

uniwind-pro@1.0.0-rc.5

React Native Version

0.83.2

Platforms

Android

Expo

Yes

Additional information

• I've searched for similar issues in this repository and found none
• I am a Uniwind Pro user

[jpudysz]

Hey this is more a question, not a bug. Moving to discussion.

[jpudysz]

When the app is building locally, the Uniwind build step (CMake etc) is slow and also makes my computer almost unusable (even though it's a M2 Pro MacBook Pro...)

Yeah, I feel you but this is how react native toolchain works. I can do nothing about it. We need to compile C++ and native files.

Any way you could provide pre-built binaries? Like it's done at https://rnrepo.org/

I can, but it's not maintainable. Why? Because prebuilds are tied to specific React Native versions.

I would need to build a binary for every React Native version we support, for example:

RC.5 for RN 0.81.0, 0.81.1, 0.82.1, and so on up to the latest version. This would take days just to release a single version.

[antoinerousseau]

you could build for the most common RN versions, and the rest would need to compile? same way RNRepo works

[antoinerousseau]

Or maybe there is a way for us to cache this, or even commit binaries

[jpudysz]

It sounds like a good idea, but unfortunately the issue is on React Native’s side, as it is not ABI stable. Even if I picked only 4 versions, it would still take me over an hour to build for each platform.

We support 4 major versions and more than 10 minor versions.

At this point, it’s unmanageable in the React Native ecosystem. Maybe this could become easier to handle in the future.