Re: Building GRPC for iOS with Bazel

[Param Reddy]

Fixing to grpc-io instead of grpc.io.

On Sat, Oct 14, 2017 at 8:44 AM, Param Reddy <pa...@spinorx.com> wrote:

Hi,

I am trying to build GRPC for iOS using Bazel in my project.  For this,  I need to use objective C(++) depending on cc_library.

Tutorials point me to use --ios_multi_cpu=armv7,arm64  as args for bazel build. This in turn gets picked as cpu based on the docs:

--[no]experimental_enable_objc_cc_deps default: "true"

Allows objc_* rules to depend on cc_library and causes any objc dependencies to be built with --cpu set to "ios_<--ios_cpu>" for any values in --ios_multi_cpu.

This causes some clash with "overload" of cpu in bazel, as some of the build scripts use "darwin" which is an OS as the cpu :-/ .  More specifically I am hitting snag at:

https://github.com/grpc/grpc/blob/master/third_party/cares/cares.BUILD#L3  This causes build to use linux config (https://github.com/grpc/grpc/blob/master/third_party/cares/cares.BUILD#L85) and failing.

Is there a reasonable way to resolve this?  Explicitly passing --cpu=darwin does not help.

Wondering if this scenario is expected to work with bazel in short term or do i need to bite the bullet and start building native Xcode projects for this.

Thanks for the help,

Param

PS:  Cross posting to both grpc and bazel groups.

[Param Reddy]

Fixed with PL:  https://github.com/grpc/grpc/pull/13011