Proto default library path Custom protoc path may lead to the error /usr/bin/include: warning: directory does not exist.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 252
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Custom protoc path may lead to the error /usr/bin/include: warning: directory does not exist.
This can happen, when the user installed the libraries into a different path. We could deal with this in a better way. Furthermore, one needs to use a workaround when using a custom protoc and custom .protol-lib as both the users .proto files and the .proto-lib needs to be contained correctly.
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
No file, test, or entry point is named. Start by tracing how custom protoc paths and custom .protol-lib paths are handled, then reproduce the missing /usr/bin/include warning with those options. Done means custom installations work without the warning and both user .proto files and the custom library are included correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100