Looks like plan-core/build-protobufs.h assumes that protoc is in the user's PATH. it used to be set up to not do this at all at this level and not require a person to do this (and just follow the instructions that were on the protobuf pages). My vision was that it was easy for visitors to build protobufs rather than do a full-blown protoc install. Does it make sense to only throw the protoc not found message if Grpc.Tools/... also can't be found? I don't want to have to mess w/ ppl's PATH just for them to build protobufs and now I'm left unable to build them on machines that don't have a full protoc install. Not getting the cons of the previous system.
Looks like
plan-core/build-protobufs.hassumes that protoc is in the user's PATH. it used to be set up to not do this at all at this level and not require a person to do this (and just follow the instructions that were on the protobuf pages). My vision was that it was easy for visitors to build protobufs rather than do a full-blown protoc install. Does it make sense to only throw the protoc not found message ifGrpc.Tools/...also can't be found? I don't want to have to mess w/ ppl's PATH just for them to build protobufs and now I'm left unable to build them on machines that don't have a full protoc install. Not getting the cons of the previous system.