Next.js ChatGPT 应用模板

Prerequisites

• Bun 1.1+ (includes Node.js compatibility): https://bun.sh/
• Rust 1.70+ and Cargo
• Android SDK (optional, for Android builds)
• Xcode + iOS SDK (optional, for iOS builds, macOS only)

Install dependencies

bun install ```

Install

Desktop install (Windows / macOS / Linux)

If espeak-ng is not on PATH, the app surfaces this same guidance at runtime. Install it once and restart the app:

• Windows

  winget install eSpeak-NG.eSpeak-NG
  

Or download an installer from the eSpeak NG releases. Make sure the install directory is on PATH so the espeak-ng command resolves in a fresh shell.

• macOS

  brew install espeak-ng
  

• Linux

  # Ubuntu / Debian
  sudo apt install espeak-ng

  # Fedora
  sudo dnf install espeak-ng

  # Arch / Manjaro
  sudo pacman -S espeak-ng
  

You can also point the app at a custom binary or data dir from the TTS settings panel, which maps to EspeakConfig { bin_path, data_path } and overrides the PATH lookup.

Setup

- Install Android Studio and let it install: - Android SDK - Android SDK Platform-Tools - Android command-line tools - Android NDK - Use JDK 17 or newer - Set these env vars in your shell startup files so both interactive shells and non-interactive bash -lc builds see the same Android toolchain:

  export ANDROID_SDK_ROOT="$HOME/Android/Sdk"
  export ANDROID_HOME="$ANDROID_SDK_ROOT"
  export ANDROID_NDK_HOME="$ANDROID_SDK_ROOT/ndk/<your-installed-ndk>"
  export NDK_HOME="$ANDROID_NDK_HOME"
  export PATH="$ANDROID_SDK_ROOT/platform-tools:$ANDROID_SDK_ROOT/emulator:$ANDROID_SDK_ROOT/cmdline-tools/latest/bin:$PATH"
  

PowerShell equivalent for the current session:

  $env:ANDROID_SDK_ROOT = "$HOME\Android\Sdk"
  $env:ANDROID_HOME = $env:ANDROID_SDK_ROOT
  $env:ANDROID_NDK_HOME = "$env:ANDROID_SDK_ROOT\ndk\<your-installed-ndk>"
  $env:NDK_HOME = $env:ANDROID_NDK_HOME
  $env:PATH = "$env:ANDROID_SDK_ROOT\platform-tools;$env:ANDROID_SDK_ROOT\emulator;$env:ANDROID_SDK_ROOT\cmdline-tools\latest\bin;$env:PATH"
  

- If you use fish, set the same values there too. The most common failure mode is having fish point at one SDK and bash -lc point at another. - Verify your environment before building:

  bash -lc 'echo ANDROID_HOME=$ANDROID_HOME; echo ANDROID_SDK_ROOT=$ANDROID_SDK_ROOT; echo ANDROID_NDK_HOME=$ANDROID_NDK_HOME; echo NDK_HOME=$NDK_HOME'
  

• Initialize the Android project once:

  bun run tauri:android:init
  

Build and Run

```bash

Build Android APK

bun run tauri:android:build ```

Setup (macOS only)

• Install Xcode from the App Store
• Install Xcode command-line tools: xcode-select --install
• Install CocoaPods: sudo gem install cocoapods (or Homebrew)
• Provide ONNX Runtime for iOS with CoreML support:
• Build/download an iOS-compatible ONNX Runtime package that includes CoreML EP
• Set ORT_LIB_LOCATION to the directory containing the ONNX Runtime libraries before building
• Initialize iOS project files:

export ORT_LIB_LOCATION=/absolute/path/to/onnxruntime/ios/libs
bun run tauri:ios:init

Build and Run

```bash

Build iOS app

bun run tauri:ios:build:ready ```

For llama-gpu-cuda, install the NVIDIA CUDA toolkit and driver on the build machine. For llama-gpu-metal, build on macOS with Xcode command-line tools installed.

Opening downloaded builds (Gatekeeper)

Release builds are ad-hoc signed, not notarized (notarization requires a paid Apple Developer account). macOS quarantines apps downloaded from a browser, so the first launch is blocked:

• On macOS 15 (Sequoia) and later: try to open the app once, then go to System Settings > Privacy & Security and click "Open Anyway".
• On older macOS versions: right-click the app and choose Open.

If Finder reports the app is "damaged and cannot be opened", clear the quarantine attribute from a terminal:

xattr -cr /Applications/lettuceai.app

Quick Start

```bash

Screenshots

CI bundle workflow

The repo ships a dedicated workflow that builds and publishes the bundle as a GitHub release asset, and the Android dev/release workflows download and verify it before each build:

- .github/workflows/espeak-android-bundle.yml — workflow_dispatch only. Inputs: tag (release tag, e.g. espeak-android-bundle-v1), espeak_ref, espeak_repo, prerelease. Uploads kokoro-espeak-android-bundle.tar.gz plus a .sha256 sidecar to the chosen release tag. - .github/espeak-android-bundle.env — pin file consumed by both Android workflows:

  BUNDLE_TAG=espeak-android-bundle-v1
  BUNDLE_ASSET=kokoro-espeak-android-bundle.tar.gz
  BUNDLE_SHA256=<sha256 of the published asset>
  ESPEAK_NG_REF=master
  

- .github/workflows/android-build.yml and .github/workflows/android-release-build.yml source the pin file, gh release download the asset into RUNNER_TEMP, verify the sha256, and export KOKORO_ESPEAK_ANDROID_BUNDLE_PATH before tauri android build.

To roll out a new bundle: dispatch Build / eSpeak NG Android Bundle with a fresh tag, copy the printed BUNDLE_TAG / BUNDLE_SHA256 block from the release notes into .github/espeak-android-bundle.env, and commit. From then on Android CI builds pick it up automatically.