Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question, importing protobuf files #468

Open
KeithWiles opened this issue Dec 10, 2024 · 3 comments
Open

question, importing protobuf files #468

KeithWiles opened this issue Dec 10, 2024 · 3 comments

Comments

@KeithWiles
Copy link
Contributor

KeithWiles commented Dec 10, 2024

I am attempting to add a new protobuf file to opi-api/network/opinetcommon directory (call it foo.proto) and import the protobuf in opi-api/network/cloud/ospf.proto file. Using import "foo.proto";

I did a make in the opi-api/network/opinetcommon directory and it seemed to compile foo.proto without any issues.

When I do a make in the opi-api/network/cloud directory I get the following output:

docker run --rm \
        -v "/Users/rkwiles/Development/opi-api/network/cloud/../opinetcommon":/opinnetcommon \
        -v "/Users/rkwiles/Development/opi-api/network/cloud":/out \
        -w /out \
        bufbuild/buf lint
ospf.proto:14:8:import "foo.proto": file does not exist
make: *** [buflint] Error 100

What am I doing wrong? Thanks for any help.

@KeithWiles
Copy link
Contributor Author

Hi Mark @sanders-mark , hope you have a great holiday.

I was hoping you have some time to point me to the answer to this question.

Thanks for any help.

@sandersms
Copy link
Contributor

Hi Mark @sanders-mark , hope you have a great holiday.

I was hoping you have some time to point me to the answer to this question.

Thanks for any help.

Hi Keith @KeithWiles
I hope that you have a great holiday also.

I have run into this issue before and will look through my notes to see how I resolved the problem. It may be after the Christmas holiday before I have the answer as we are off for the next week; but, will get back to you regarding what I had uncovered to resolve the issue.

Thanks,
Mark

@KeithWiles
Copy link
Contributor Author

KeithWiles commented Dec 20, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants