You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering an issue while using rules_swift_package_manager to import third-party Swift package dependencies into my project. The linker path includes a non-existent directory, -LNone.
While this currently doesn't cause linker errors, it's concerning to have a non-existent path in the linker configuration. Additionally, None is a reserved keyword in both Python and Starlark(Bazel's build language), which could potentially lead to confusion.
I made a demo repository that demonstrates three different build methods:
SPM: Uses swift run for building.
Bazel with rules_swift_package_manager: Use CC=clang bazel build //Sources:test-bazel-swift-atomics
Bazel with Manual BUILD File: Use CC=clang bazel build //Sources:test-bazel-swift-atomics-alt
For easier reproduction, a GitHub action running the build command has been included. You can access the build log here: link to build log
The following snippet displays the linker command generated by Bazel with rules_swift_package_manager:
I'm encountering an issue while using
rules_swift_package_manager
to import third-party Swift package dependencies into my project. The linker path includes a non-existent directory,-LNone
.While this currently doesn't cause linker errors, it's concerning to have a non-existent path in the linker configuration. Additionally,
None
is a reserved keyword in both Python and Starlark(Bazel's build language), which could potentially lead to confusion.I made a demo repository that demonstrates three different build methods:
swift run
for building.rules_swift_package_manager
: UseCC=clang bazel build //Sources:test-bazel-swift-atomics
CC=clang bazel build //Sources:test-bazel-swift-atomics-alt
For easier reproduction, a GitHub action running the build command has been included. You can access the build log here: link to build log
The following snippet displays the linker command generated by Bazel with
rules_swift_package_manager
:As you can see, the
-LNone
flag is present in the linker path.The text was updated successfully, but these errors were encountered: