-
Notifications
You must be signed in to change notification settings - Fork 69
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
Argument header not a recognized key, 'strict_include', or 'providers'. #232
Comments
I hit the same problem. I guess this is caused by breaking changes made by Bazel and its default apple rules. Our setup is
|
veblush
added a commit
to grpc/grpc
that referenced
this issue
Apr 21, 2023
Oops I missed important changes from #32712. And it turned out that there are two problems that I couldn't fix at this point. - Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6 invokes build tools chain but it's not clear. I put workaround to use Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1` - Rule `rules_pods` to fetch CronetFramework from CocoaPod has incompatibility with sort of built-in apple toolchain. (bazel-xcode/PodToBUILD#232): I couldn't find a workaround to fix this so I ended up disabling all tests depending this target.
I’m dealing with the same problem as you. |
XuanWang-Amos
pushed a commit
to XuanWang-Amos/grpc
that referenced
this issue
May 1, 2023
Oops I missed important changes from grpc#32712. And it turned out that there are two problems that I couldn't fix at this point. - Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6 invokes build tools chain but it's not clear. I put workaround to use Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1` - Rule `rules_pods` to fetch CronetFramework from CocoaPod has incompatibility with sort of built-in apple toolchain. (bazel-xcode/PodToBUILD#232): I couldn't find a workaround to fix this so I ended up disabling all tests depending this target.
wanlin31
pushed a commit
to grpc/grpc
that referenced
this issue
May 18, 2023
Oops I missed important changes from #32712. And it turned out that there are two problems that I couldn't fix at this point. - Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6 invokes build tools chain but it's not clear. I put workaround to use Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1` - Rule `rules_pods` to fetch CronetFramework from CocoaPod has incompatibility with sort of built-in apple toolchain. (bazel-xcode/PodToBUILD#232): I couldn't find a workaround to fix this so I ended up disabling all tests depending this target.
This patch may provide a temporary solution to this issue.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ERROR: /Users/#####/Desktop/macosclient/Vendor/Alamofire/BUILD.bazel:219:16: in umbrella_header rule //Vendor/Alamofire:Alamofire_umbrella_header:
Traceback (most recent call last):
File "/Users/#####/Desktop/macosclient/Vendor/rules_pods/BazelExtensions/extensions.bzl", line 113, column 51, in _umbrella_header_impl
objc_provider = apple_common.new_objc_provider(
Error in new_objc_provider: Argument header not a recognized key, 'strict_include', or 'providers'.
ERROR: /Users/#####/Desktop/macosclient/Vendor/Alamofire/BUILD.bazel:219:16: Analysis of target '//Vendor/Alamofire:Alamofire_umbrella_header' failed
ERROR: Analysis of target '//IRMClient:IRMClient' failed; build aborted:
INFO: Elapsed time: 0,083s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 42 targets configured)
The text was updated successfully, but these errors were encountered: