-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Can't depend on non-cc_library
libraries in libs
#114
Comments
I think you mean 'deps', not 'libs'. Allowing genproto in deps of Let me try to describe the model of how I think this should work: cc_library.srcs -> this is a bit tricky; gcc takes a lot of different If you want to import other files, such as precompiled .jar or .so files, When you want to use a proto rule, the main question is, does it have a (I would also like to merge the various Cc*Providers into a single Internally, we have a proto_library rule which has both the Java and C/C++ This is also not implemented yet, at least not entirely. We have parts of This ended up a bit long. Short answer is, for now, generate .c / .cc files On Mon, Apr 13, 2015 at 6:53 PM, zrlk notifications@github.com wrote:
|
ulf, can we close this, or is there something left to do? |
I'm closing this as there's no short term action item here. Longer term, we may want to audit the rules and lock down the semantics (but then again, we may never get to that because so much else is important). :-( |
I'm just wondering - what's the status on this? I've found proto_library (http://bazel.io/docs/be/protocol-buffer.html) but it has little to no documentation, and I can't seem to get it to work with cc_library. What's the current protocol (no pun intended) for building and using proto messages with a cc_library? |
We don't have an out-of-the-box solution for proto messages with cc_library, yet. proto_library is undocumented because it's not ready yet, and it won't work the same way as proto_library works inside Google (in case you have knowledge of that). Sorry, this is all very vague and handwavy - we should really publish our plans around proto_library support. Maybe file a feature request for C++ protobuf support? |
* Add md5sum function * Add md5 rule for tests * Add --experimental_enable_runfiles for Windows ci tests * Fixes bazelbuild#109
It's unclear why Bazel forbids depending on rules that are not instances of the builtin
cc_library
forlibs
inputs to other rules. This would allow, among other things, a C++ version ofgenproto
. (The Java version works because the code explicitly allows it: see bazel/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java:118).The text was updated successfully, but these errors were encountered: