Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Android AAR / Maven packaging for projectM

Aperta
  • Qualcosa non va?
#999 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
android, cmake, cpp, github-actions
Ambito
build-system, mobile, release

Direzione di ricerca

Start with the linked projectm-android-builds repository and its usage documentation, then compare its upstream build workflow, AAR/Prefab output, and GitHub Actions publishing setup with projectM's needs. The issue has no named projectM files or tests; completion would require maintainer agreement on official Android packaging, repository hosting, and debug/release artifact conventions.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

question
Please confirm the following points:
  • This question is NOT about the Android apps in the Play Store
  • I have searched the project page to check if the question was already asked elsewhere
Topic

Development and Contributing

Your Request

Hi everybody, I wanted to let you know that I created an automated Android build and publishing setup for projectM:
https://github.com/protyposis/projectm-android-builds
Usage docs: https://protyposis.github.io/projectm-android-builds/

It tracks projectM releases/branches, builds Android AAR packages (by reusing the upstream build workflow), and publishes them to a custom Maven repository (hosted on GitHub Pages), all fully automatic via GitHub Actions. The AAR uses Prefab so Android projects can consume the native projectM libraries very easily through Gradle/CMake.

I did not publish the artifacts to an official Maven repository because I think that should either be done by, or at least endorsed by, the projectM maintainers. I am also not fully sure about the artifact setup: it currently includes both debug and release builds, and the Android build tools automatically select the debug libraries for debug app builds.

Anyway I thought this could be useful for other Android developers using projectM. I'm open to suggestions and would also be happy to contribute the setup upstream.

Background: I created this for idiomatic dependency management in an Android projectM app I built. I regularly enjoy projectM on my Android TV, and actually just wanted the existing Android app from the Play Store to display now-playing title/artist information, so I modded it to make it work, and offered the author help with updating his app. He declined, and since I was unhappy with the overall UX I built this new app based on the latest projectM version :) Happy to get feedback on it as well.

Lingua principale
C++
Stelle
4.6k
Fork
498
Merge medio
3g 14h
PR unite (30g)
4

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di projectM-visualizer/projectm

Tutte le issue di projectM-visualizer/projectm

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.