Refresh components
Refresh the managed ecosystem under ~/.macoraone/ by cloning the configured component repositories again.
one install
Find anything
Search the documentation
Search commands, components, examples and project guides. The index is separate from page markup so new entries can be added without rebuilding the page layout.
Quick start
Build and install the CLI
Build from the repository on Linux with a C11 compiler and Make.
git clone https://github.com/MacoraOne/MacoraOne.git cd MacoraOne make clean all make test ./one --version ./one --help
To install the executable system-wide, the repository documents sudo make install. Review the Makefile and source before installing software with elevated privileges.
Commands
Core workflows
The controller coordinates Android templates and dynamically discovered greenServeFE release packages.
Create an Android app
Authenticate with GitHub CLI, choose Java or Kotlin, then create a local project and GitHub repository from the matching NativeFlexi template.
one create WeatherApp
Push project changes
Push the local app tree to the target repository. This workflow is documented as an override of the target branch's current tree—check the destination before running it.
one push WeatherApp WeatherApp one push WeatherApp owner/WeatherApp
Build through Actions
Dispatch the matching Java/Kotlin workflow, follow its logs, and show the GitHub Actions artifact page after a successful build.
one build WeatherApp
Install native packages
Discover release assets from the greenServeFE GitHub Releases API and install an engine or module by package name.
one install greenServeFE one install gsnum one install gsnum@1.0.0 one list-available
Manage installed packages
List installed versions or remove a managed package. The global uninstall removes the whole MacoraOne managed directory.
one list one uninstall gsnum one uninstall
Project lifecycle
From template to APK
Authenticate with GitHub
Install GitHub CLI (gh) and sign in using its browser-based login when prompted.
Choose a template
one create AppName refreshes NativeFlexi, asks for Java or Kotlin, and copies only that template and its matching manual workflow.
Edit ordinary Android files
Use Gradle, Java/Kotlin, XML layouts, resources and AndroidManifest.xml as usual. There is no custom NativeFlexi language.
Push and build
Push your app and dispatch the corresponding GitHub Actions workflow; download the APK from the resulting artifact page.
Architecture
Existing projects remain the source of truth
| Component | Role | Implementation |
|---|---|---|
| NativeFlexi | Android app templates | Java/Kotlin + Gradle + Android SDK |
| greenServeFEGSVE Examples | Bytecode runtime and native modules | C11, Makefile, release ZIP assets |
| CMLLCMLL Examples | Command-oriented scripting language | C implementation and .cmll source |
| MVM | Reusable bytecode execution engine for language implementations | C11 API, stack VM, native callbacks and profiler |
Security note: GitHub credentials are handled through GitHub CLI. Do not store tokens, passwords or Android signing keys in source files. Review a push target before using the documented override workflow.
Source