Bazel

Bazel-based mobile projects use a rebuild-based dev loop. Revyl detects Bazel workspaces by looking for MODULE.bazel, WORKSPACE.bazel, or WORKSPACE files. Bazel is a build tool, not a supported build.framework value. When Revyl finds one native app platform, revyl init authors an ios- or android-oriented profile using the inferred Bazel command or a placeholder for you to complete. When the workspace spans both native platforms, init writes project and session configuration only. Configure each native app as its own platform-oriented Revyl project rather than authoring legacy build.system or build.platforms fields.

What `revyl init` shows

Detected: Bazel
  Platforms: android, ios
  Bazel workspace detected with concrete android and ios targets.
  Writing project and session configuration only; no build profiles were added.

Example configuration

build:
  framework: ios
  profiles:
    development:
      ios:
        build_commands:
          - "bazel run //tools:generate_mobile_sources"
          - "bazel build //ios:MyApp -c dbg"
        output_path: "bazel-bin/ios/MyApp.app"

For an Android app, use framework: android and an android recipe in that app’s project config. Run revyl config validate after authoring the recipe.

Getting Started

CLI

Builds

Tests

Develop

Atlas

Integrations

Appendix

What `revyl init` shows

Example configuration

​What revyl init shows

​Example configuration

What `revyl init` shows

Example configuration