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

On Sat, Oct 14, 2017 at 8:46 AM, Param Reddy <[email protected]> wrote:

> Fixing to grpc-io instead of grpc.io.
>
> On Sat, Oct 14, 2017 at 8:44 AM, Param Reddy <[email protected]> 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.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CA%2Bs%3DH07%3Do_tonyKawGo_y98fvgcSaUt0LgW_e-e%3DC4U_QeCc%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to