Should there be a guide for people doing development on Npcap?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to figure out how to profile a test program (it runs pcap_findalldevs() many times, to try to figure out where the CPU time is going), but apparently this may require 1) .pdb files for wpcap.dll and packet.dll and 2) might also require building the libraries with /PROFILE.
Should there be a guide for people doing development work on Npcap itself, indicating how to set up the development environment? It might belong in the "Npcap internals" documentation.
Contributor guide
No contributing guide indexed for this repository
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 existing "Npcap internals" documentation and the pcap_findalldevs() profiling scenario described in the issue. Document the development-environment setup, including the role of .pdb files and /PROFILE-built libraries. Done means a developer can follow the guide to prepare Npcap for profiling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100