MobileNativeFoundation / rules_xcodeproj

Bazel rules for generating Xcode projects.
MIT License
521 stars 83 forks source link

Bug: `bazel_path` breaks when used in a case-sensitive file system when Bazel wrapper is in `Tools/bazel` #3025

Closed luispadron closed 4 months ago

luispadron commented 4 months ago

Description

We keep our wrapper in a uppercased Tools/bazel directory. In a case-insensitive file system the check done here: https://github.com/MobileNativeFoundation/rules_xcodeproj/blob/7683faee63343c3410c4c40ea13f5adc5bae43b7/xcodeproj/internal/templates/runner.sh#L93 works fine. However, on a case sensitive file system the logic breaks and leads to other issues (we validate this is set in our wrapper and fail the build)

Reproduction steps

Expected behavior

This works for both Tools/bazel and tools/bazel

rules_xcodeproj version

2.2.0

Xcode version

15.1

Bazel version

6.5.0

rules_apple version

No response

rules_swift version

No response

Additional information

No response

luispadron commented 4 months ago

I'll get a fix for this up today

luispadron commented 4 months ago

Im going to close this, turns out this is a limitation of bazelisk and using Tools/bazel is not supported in a case-sensitive file system