Build and package

This guide summarizes the workflows downstream app developers use most:

• run an app locally during development
• bundle and package an app for distribution
• install onto a device/target
• prepare update artifacts and serve them

1) Install toolchain dependencies#

For host builds, oroc setup with no --platform installs dependencies for your host OS. To target a platform:

oroc setup --platform=android
oroc setup --platform=ios

See: oroc setup.

2) Development loop#

From your project directory:

oroc run .

Common knobs:

• -D/--debug or ORO_DEBUG=1 for debug mode
• -V/--verbose or ORO_VERBOSE=1 for verbose logging
• --log-file=... to mirror logs to a JSON file

If you want file watching during development, use webview.watch / webview.watch_reload in oro.toml.

See: oroc run and Configuration reference.

3) Bundle inputs with copy_map#

Copy-maps define exactly what files are included in your app bundle.

"./src/index.html" = "index.html"
"./src/main.js" = "main.js"

See: copy_map.

4) Add a web build step (optional, common)#

Many apps run a web build step (Vite, Rollup, etc.) and then map the generated output into the runtime bundle.

Use build.script to run your web build before the copy phase:

[build]
script = "./scripts/build-web.sh"
copy_map = "copy-map.toml"

5) Production build + packaging#

For a production build:

oroc build . --prod --package

Packaging is platform-specific (for example Linux deb/rpm, macOS zip/pkg, Windows appx). See:

• oroc build
• Configuration reference

6) Install onto a device/target#

List devices:

oroc list-devices --platform=ios
oroc list-devices --platform=android

Install:

oroc install-app --platform=ios --device <identifier>
oroc install-app --platform=android --device <identifier>

See: oroc list-devices and oroc install-app.

7) Build update artifacts (optional)#

Update tooling can:

• scaffold and validate update manifests
• bundle app artifacts as tar files
• sign and verify manifests
• run an update server (HTTP/TCP/UDP)

See: oroc update.