If you are using gRPC as a user (not contributing to the gRPC codebase),
then using only released versions (=that have a release tag) of gRPC is the
recommended approach.

Ad the "unable to remove directory": not sure what the cause is in your
case, but from git perspective, tags and branches are essentially the same
kind of thing internally, so using a release branch vs using a release tag
likely won't change anything.

Updating submodules:
Yes, you need to update submodules yourself (that's how submodules work).
Basically, run "submodule update --init" anytime you switch between commits
of the grpc/grpc repository to make sure submodule are up to date. If your
submodules are out of date, you likely won't be able to build.

On Tue, Oct 29, 2019 at 7:31 PM <[email protected]> wrote:

> I'm using this <https://github.com/grpc/grpc/blob/master/BUILDING.md> guide
> to build gRPC from source. One question about the use with git. What I'm
> doing when a tag (v1.24.1, v1.24.2,...) is released i just checkout this
> tag. My first question is, is this a good approach to just working on tags.
> Because sometimes i'm getting errors like "unable to remove directory
> ....". Or is it better to be on the v1.24.x branch and pull changes from
> there?
>
> Second question is how to update the submodules in the third_party folder.
> Do i have to update the submodules by myself?
>
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/a602a651-8535-4e57-b5d2-ee696e92f4a3%40googlegroups.com
> <https://groups.google.com/d/msgid/grpc-io/a602a651-8535-4e57-b5d2-ee696e92f4a3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 

Jan

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CACF4M0R2Z8Rvvvi5biNHoPxTHWn3TN4TDtUEhfUqasUEO8d51Q%40mail.gmail.com.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to