Closed TheButlah closed 8 months ago
This issue has 12 upvotes, and since bazel's support for cc_shared_library and fully_static_link seemed so poorly documented if not fully unusable, I have stopped using bazel.
Has any progress been made in the last year and a half?
Looks like this can now be closed: https://bazel.build/reference/be/c-cpp#cc_shared_library
Description of the problem / feature request:
Could some documentation be provided for the
cc_shared_library
rule? I'm finding that its the only way for me to produce a.so
file for use in non-bazel projects, but the lack of documentation makes it unclear to me what the different attrs are supposed to be used for.Feature requests: what underlying problem are you trying to solve with this feature?
Figure out how to produce
.so
files for use outside of bazel (cc_binary
doesn't seem to include symbols for its dependencies?)What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
master
branch as of 20 Oct 2020Have you found anything relevant by searching the web?
Googling yields some references to using
cc_binary
to produce the.so
, but I haven't gotten this to work. So far onlycc_shared_library
has worked.