-
Notifications
You must be signed in to change notification settings - Fork 93
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
Support cc_embed_data #41
Comments
Here is the implementation (hand written): https://github.com/google/iree/tree/master/build_tools/embed_data |
FWIW, LLVM needs this as well, and it is challenging to use this implementation. (Abseil and other dependencies that we shouldn't need to pull down and put in the host build just for this...) Is there any chance of progress here, or should we too roll our own? |
It shouldn't be hard to remove the abseil dep, and in hindsight I shouldn't have taken it. I don't have any plans to evolve this further unless if a need emerges for us. Feel free to grab anything we have to bootstrap rolling a new one, and if you get a dep-cleaner version, we can grab that back when it is ready. |
For now, trying to avoid the need, but will do if it ends up necessary. |
I'd also +1 this, as I'd like to use cc_embed_data in https://github.com/google/distributed_point_functions/. |
Xoogler here. I'm happy to take on this task of upstreaming this into Bazel as my first contribution. @chandlerc @stellaraccident It's hard for me to unwind the threads but it seems your implementation doesn't actually have a dependency on abseil? |
Yeah, it should be dependency clean. Looks like its grown a couple of define checks in the generated code but should be easily removed. Feel free to take it if it is helpful. |
Description of the problem / feature request:
Bazel doesn't support cc_embed_data
Feature requests: what underlying problem are you trying to solve with this feature?
I would like to embed data into C++ code.
We ended up having to hand-roll our own: iree-org/iree@4be1097
Feel free to take code from there. I don't think we have time to upstream this properly.
The text was updated successfully, but these errors were encountered: