studio

onerom-studio

A GUI front-end for interacting with One ROM and managing firmware images.

Releasing

All instructions assume you are in the rust/studio directory. Steps 1-3 can be run in parallel.

Steps:

1. Copy the schema to the images repo if it differs. The schema is regenerated when the version is updated.

   git diff manifest/app-schema.json ../../../one-rom-images/studio/app-schema.json
   # If differences
   cp manifest/app-schema.json ../../../one-rom-images/studio/app-schema.json

2. Use the build-release.sh script to build Studio for all platforms and architectures. This requires ssh access to build machines for each platform and clones the current main branch to build from. To set up the Windows machine, see Setting up a Windows build machine:

   scripts/build-release.sh pin=WIN_SIGNING_PIN

   Artifacts are placed in the dist/ directory.

3. Run the release script to upload the files and update the manifest - assumes you have the images.onerom.org github repo at ../../../one-rom-images:

   scripts/release.py --input-dir dist --output-dir ../../../one-rom-images

4. Commit one-rom-images changes and push:

   cd ../../../one-rom-images
   git add .
   git commit -m "Update One ROM Studio releases"
   git push

5. Tag the current commit in one-rom and push. Tags are signed, so they take a message:

   cd ../one-rom
   git tag -s -a studio-vX.Y.Z -m "One ROM Studio vX.Y.Z"
   git push origin studio-vX.Y.Z

6. Check new releases appear at https://onerom.org/studio/

7. Update the Studio manifest one-rom-images/studio.json with the latest version.

Updating Mac Icons

1. From an up to date Apple Silicon Mac, open assets/onerom-liquid-glass.icon.

2. Modify the icon as needed using the Icon Composer application.

3. Regenerate assets/onerom-liquid-glass-icons/Assets.car using:

   scripts/create-mac-icon-ac.sh

4. Commit and push both assets/onerom-liquid-glass.icon and assets/onerom-liquid-glass-icons/Assets.car.

Creating a new Code Signing Certificate

See https://piers.rocks/2025/10/30/certum-open-source-code-sign.html

CI

.github/workflows/build-apps.yml builds the Studio and CLI Windows and macOS packages, and .github/workflows/ci.yml builds and tests the Linux packages. These packages are unsigned, so do not use them for release.

Both run on every push that changes rust/.

Dependencies

Assuming building Windows target on a Debian-based Linux distribution.

Install the Rust Windows targets:

rustup target add x86_64-pc-windows-gnu

Install ming-w64 for Windows builds:

sudo apt install mingw-w64

Packaging Implementation

Windows

Uses cargo-packager - see the following in Cargo.toml:

• [package.metadata.packager]
• [package.metadata.packager.nsis]

Code signing is done using signtool.exe called from scripts/build-windows.ps1.

macOS

Uses cargo-bundle to create the macOS app bundle - see the following in Cargo.toml:

• [package.metadata.bundle]

scripts/build-mac.sh does code signing and notarization using codesign and xcrun notarytool.

scripts/create-dmg.py is used by build-mac.sh to create DMG installer.

Linux

scripts/build-linux.sh builds x86_64 and arm64 .deb packages, on either architecture, using cargo-zigbuild and cargo-deb - see [package.metadata.deb] in Cargo.toml. The packages require the glibc version in ci/linux-min-glibc-version or later, whatever the build machine runs, and include maintainer scripts to handle udev rules installation.