add validate command that checks for portability of shared libraries
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
Plan on adding node-pre-gyp validate command.
We can programmatically query the built binary module, scan for dynamic shared library dependencies, and do various diagnostics/sanity checks.
- OS X:
otool -L(or https://github.com/nico/lssym) - Linux:
lddorreadelf -d - Windows: depends.exe (https://github.com/mapbox/mapbox-studio/blob/mb-pages/test/check_shared_libs.py#L38-L57)
At the least the command should print some diagnostics for the developer to inspect:
- What shared libraries are depended upon (and what do they depend on)
- On OSX / Linux do any shared libraries occur with absolute rpaths in locations like
/usr/local/lib(which would indicate linking happened to non-portable library)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the planned node-pre-gyp validate command and review the platform tools named in the issue: otool or lssym, ldd or readelf, and depends.exe. Done means the command reports shared-library dependency chains and flags non-portable absolute rpaths on OS X and Linux.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100