Replace Python-based shared object test with a C++-only version #62
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The shared object test has dependencies on both Python and pkg-config (in order to locate libpython and Python's headers). It dates back to a time when the C/C++ and Python rules were both part of the main Please repo, but now that they live in separate plugin repos, importing the python-rules plugin (and expecting Python and pkg-config to be installed system-wide) is excessive for the sake of a single test that doesn't strictly require Python to prove that cc-rules' dynamic linking functionality works as expected.
Eliminate libpython from the ABI between the shared object and test binary. What remains is enough to prove that cc-rules is generating valid shared libraries that are loadable at run-time by dynamically-linked binaries.