Goal: eliminate the necessity for neon-cli to wrap cargo so Neon projects can directly use all cargo commands in the Rust source directory.
Ideas:
- Specify link flags in manifest
- On macOS need to pass
-C link-args=-Wl,-undefined,dynamic_lookup - Want users to be able to just type
cargo build
- Post-build hook
- Need to generate the final dylib as a
.nodefile in the right path (by copying from the Cargo output)
- Infer target from environment
Neon developer ends up specifying it once for npm via env var and once for cargo via --target. Would like this to be DRY.
- Custom cache validation
- Want to store various build settings in a config file to determine whether cached code is invalid.
- Needs to be based on several inputs including environment variables and Cargo settings.
- Wants to augment not replace existing Cargo invalidation policy.