bazel-contrib / bazel-contrib/rules_go
C++ interop and swig
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 762
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 12
Description
I see in the top-level README.md that there is no support at the moment for C++ interop. However, I also see that there *is* support for cgo.
What work is required to properly compile .swigcxx files in a package?
I'm hacking together a workaround for the package I'm using, but I'm willing to do this properly and submit a PR. Any pointers about the "right" way to do this?
Contributor guide
Research direction
Read the top-level README.md and the existing cgo support first, then trace how a package’s .swigcxx files are currently handled. Done means the required C++/SWIG interop behavior is defined and package compilation works, with a clear way to validate it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100