With bazel still not being stable (current version being 0.24), its API is subject to change rapidly and it's difficult for us to keep up to date. As a result, our current bazel files are really going to work fine with bazel 0.23.2 at the moment. Buyers beware.
This being said, integrating grpc as a bazel dependency is doable. It's not 100% easy, due to the way bazel doesn't handle transitive dependencies at the moment, but here's an example on how this is supposed to work: https://github.com/googlecartographer/cartographer/blob/master/WORKSPACE Basically, you import our grpc_deps function, and invoke it in your workspace. This should register all of our dependencies into your workspace. On Monday, April 22, 2019 at 11:42:10 AM UTC-7, [email protected] wrote: > > Hi, > > I would like to incorporate grpc into my existing bazel workspace so grpc > can be automatically built as a dependency. > > I realize that there have been so many changes introduced to > grpc/protobuf/bazel since the last time I did that. I wonder what's the > recommended way of doing that today. Should I just use local_repository and > expect that should work? > > Thanks, > Ming > > > -- 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/4ca4afe1-6438-4007-bf34-7cb02c46372c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
