-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel instructions result in missing rules_xcodeproj
#4737
Comments
I've just bumped into the same issue. It looks like SwiftLint currently require @mattrobmattrob I think the second issue is because the Bazel version you're using has |
This was needed because the `xcodeproj` target was declared in the same BUILD file with the `@SwiftLint//:swiftlint` target, so when users run `bazel run @SwiftLint//:swiftlint`, bazel would try to load `rules_xcodeproj`. This only fixes for non-bzlmod case now. Fixes realm#4737
This was needed because the `xcodeproj` target was declared in the same BUILD file with the `@SwiftLint//:swiftlint` target, so when users run `bazel run @SwiftLint//:swiftlint`, bazel would try to load `rules_xcodeproj`. `rules_xcodeproj` 1.0 allows us to specify the location of the generated Xcode project, so we don't need this target in the top-level BUILD file anymore. This only fixes for non-bzlmod case now. Fixes realm#4737
New Issue Checklist
Describe the bug
Lack of
rules_xcodeproj
definition when following theWORKSPACE
+bazel run -c opt @SwiftLint//:swiftlint
README.md definition in a workspace that doesn't already definerules_xcodeproj
.Complete output when running SwiftLint, including the stack trace and command used
Environment
WORKSPACE
to usebazel run -c opt @SwiftLint//:swiftlint
:And then when a manual
rules_xcodeproj
is added to theWORKSPACE
, the result is:The text was updated successfully, but these errors were encountered: