Support for NuGet packages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.7k
- Forks
- 1.9k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
There doesn't seem to be a way for node-gyp to generate a packages.config + required goop in the generated vcxproj, so that certain NuGet packages are referenced by the generated project.
Our project references a couple of NuGet packages, which bring in Windows metadata files (.winmd), headers and build-time logic (cppwinrt).
The workaround for now seems to be to check in the generated headers instead of relying on cppwinrt generating the headers at build time, however this is fragile as different cppwinrt versions are not necessarily ABI compatible.
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 by examining how node-gyp generates the Visual C++ project and how the generated project could represent packages.config dependencies. The work is done when generated projects can reference the required NuGet-provided metadata files, headers, and build-time logic without checking in generated headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100