mirror of
https://github.com/nolen777/eagle0.git
synced 2026-07-28 22:35:42 +00:00
258f739d02
* Move SparklePlugin to separate Bazel workspace to resolve rules_swift conflict The problem: grpc 1.76.0.bcr.1 requires rules_swift 3.x, but rules_apple 4.x requires rules_swift 2.x. These have different compatibility levels, causing bzlmod resolution to fail when both are in the same workspace. The solution: Move SparklePlugin (the only thing using rules_apple) to a separate Bazel workspace at `sparkle_workspace/`. This workspace has its own MODULE.bazel with only rules_apple and Sparkle dependencies, completely isolated from the grpc/flatbuffers dependency tree. Changes: - Create sparkle_workspace/ with isolated MODULE.bazel - Move SparklePlugin source files to sparkle_workspace/ - Update build_sparkle_plugin.sh to build from subworkspace - Remove rules_apple from main MODULE.bazel - Add single_version_override for rules_swift 3.1.2 (for grpc/flatbuffers) All 315 tests pass. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Add WORKSPACE.bazel to sparkle_workspace to prevent parent workspace detection Without this file, Bazel may walk up the directory tree and find the parent workspace's MODULE.bazel, causing dependency conflicts. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
The file is empty.