Stop using Python for the linker wrapper

Open
#49 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start by locating the linker wrapper and the Python invocation described in the issue, then inspect how it calls the Android NDK standalone packaging script. Done means the wrapper no longer requires Python while preserving its linker behavior; the issue names no tests, so identify the relevant verification path.

Written by the indexing model from the issue text.

Description

While poking around this project for the first time in a long time, I noticed that we require Python. I couldn't remember why, and it turns out we're only invoking Python in the linker wrapper. It seems silly to route through Python for this.

I think that when this was implemented we needed Python to invoke some Android NDK standalone packaging script, so it made some sense to use Python and not fuss with Windows batch files any more than needed. But now, it would be grand to have one fewer major dependency.

Dominant language
Kotlin
Stars
1.3k
Forks
95
Avg merge
15m
Merged PRs (30d)
2

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.

More from mozilla/rust-android-gradle

All issues in mozilla/rust-android-gradle

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.