-
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
cc provider digestable from Skylark rule implementation #2163
Comments
Hi Andreas, what you describe is what we internally call "sandwich" (design doc). We have some rudimentary support for taking CcLinkParams from one native rule and passing it to another native rule, but not much more. The good news is that we are going to work on this very soon, hopefully in January. The prerequisite cleanup and preparation work is already happening. |
Just an update, still cleaning stuff up, actual work on C++ sandwich hasn't yet started. |
@mhlopko hey, did the work start ? :) |
Yes :) @ventrescadeatun is already investigating how the api should look like and doing the required cleanups. Design doc will be shared in Q1. |
Awesome! Thank you for the quick response |
@mhlopko Has there been progress on this issue, and/or did the design doc get published yet? |
I have a prototype and I am planning to send it for review to the Skylark people sometime in the next few weeks. I will update this issue: #4570 |
I'm closing this one, both CcToolchainInfo and CcInfo are fully released and exposed to Starlark. |
Description of the problem / feature request / question:
I have a rule implementation, which generates a C++ header. This header then needs to be includeable by its name alone. Naively looking at
CcSkylarkApiProvider
I would do the following:Which leads to the error message:
So it seems like there is no way of defining and digesting
cc
Provider in Skylark.Environment info
Operating System: Ubuntu 16.04.1
Bazel version (output of
bazel info release
): 0.4.1Anything else, information or logs or outputs that would be helpful?
Nope.
The text was updated successfully, but these errors were encountered: